I sometimes try to open a file from a terminal and pass the wrong path. Asking the user to confirm the new file solves this problem, they can easily press escape to cancel the new document.
Occasionally I might use a glob that turns out to be wrong too, creating many unwanted new documents. So I made cancelling a new document ignore any remaining new filenames passed to Geany.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2369
-- Commit Summary --
* Ask whether to open new files from command-line
* If new document cancelled, ignore remaining new filenames
-- File Changes --
M src/libmain.c (24)
-- Patch Links --
https://github.com/geany/geany/pull/2369.patchhttps://github.com/geany/geany/pull/2369.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/2369
In certain places (window title, some dialog titles, tab bar, ...) we shorten the document name to 30 or sometimes 100 characters by removing characters in the middle of the document name and replace it by "…".
This was initially introduced by a request in https://sourceforge.net/p/geany/bugs/298/.
On the mailing list (https://lists.geany.org/users/2019-March/010970.html), it was requested to disable this feature.
One possible implementation could add two new "Various preferences" to make the currently used constants (30 and 100) configurable, with `0` as disabling the feature and add some documentation for these settings.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/2112
Add saving project state by changed, please.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/1334
I switched today from Geany 125 to 126 With the new version (running on Windows 7 64bit), I have (reproducibly) a strange problem with one file (its name is `irbrc`) which I had created with 125: When I want to save the file, an error popup occurs (see screenshot) which gives a "permission denied" message Moreover, this popup can not be clicked away (more precisely, when I click on OK, the popup seems to disappear for a fraction of a second, only to reappear again) I think, this behaviour of the popup window is clearly an error, because it is a modal dialogue, and I have to kill Geany with the task manager in order to continue my work It could be that Geany, after I clicked OK, tries again to fulfil the *Save* request, and finds - for whatever reason - the file still write-protected and brings up the same dialogue again
BTW, I don't think that this is *really* a permission issue, even though the message says so, because I can happily edit this file with other text editors I don't know why this file is special It is neither the name nor the content - I can use "save as" to save the file into a different directory
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/815
This may already be on the developer's to-do list, but I think it would be very helpful if the Debugger add-on had support for PDB (Python Debugger) and LLDB (LLVM Debugger).
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/886
I currently have two Geany instances open. One is being used for a dedicated project; the other is a "scratch" instance I keep open for general-purpose rapid iteration.
I don't mind using the GNOME filepicker to open/save files when working on dedicated projects, but I tend to prefer the terminal for speed when I'm rapidly opening and closing things or when I need to create quick hacks without breaking mental flow.
Unfortunately, Geany wants to send *everything* to its "first instance" when invoked at the commandline. Due to coincidence, apparently this is the instance with the dedicated project in it. Soooo, I get to use the terminal with my dedicated projects, but am forced to use the filepicker (over NFS!!!) when doing quick hacks. Haha.
So. I found Geany's `--socket-file` parameter, but I do not understand how to use it *as only the master Geany instance has a socket file in `/tmp`!*
```
$ ls .config/geany/
colorschemes filedefs geany.conf geany_socket_darkstar__0 keybindings.conf plugins tags templates
$ readlink .config/geany/geany_socket_darkstar__0
/tmp/geany_socket.b5c4f11f
$ lsof | grep geany_socket
geany 17853 i336 5u unix 0xc2b68240 0t0 4654382 /tmp/geany_socket.b5c4f11f
$ ls /tmp/geany_socket*
/tmp/geany_socket.b5c4f11f
$ ps aux | grep [g]eany
i336 17853 0.1 1.7 103224 36696 ? Sl Mar04 74:50 geany
i336 17955 0.0 1.6 105060 34036 ? Sl Mar04 25:23 geany
$
```
I'm curious why `--socket-file` exists at all. There are no options that allow me to start an instance with a specified socket file of my own choosing, for instance; I have to rely on Geany creating the socket file itself so I can use it.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/1834
The "Macro Trigger" entry doesn't respond to key presses. To reproduce, choose `Tools ->Record Macro`, then try to press some keys while the cursor is in the `Macro Trigger` entry.
Windows
Geany v1.35
Plugins v1.35
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/850
A more appropriate highlighting for keys in YAML files. The improvement can be noticed in any color scheme, particularly in the default one, where keys would have the same color and face than the ordinary text.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1838
-- Commit Summary --
* Better highlighting for YAML keys
-- File Changes --
M data/filedefs/filetypes.yaml (1)
-- Patch Links --
https://github.com/geany/geany/pull/1838.patchhttps://github.com/geany/geany/pull/1838.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/1838
all other types, including user defined structs are correctly highlighted but not this basic type
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/2314