$XDG_RUNTIME_DIR is the place where to put socket files these days.
It seems good practice to create a sub-directory as well, perhaps we
create more files there in the future.
The fallback to write in /tmp remains for the rare occasions where
$XDG_RUNTIME_DIR cannot be used.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2222
-- Commit Summary --
* prefer XDG_RUNTIME_DIR over /tmp for the socket
-- File Changes --
M src/socket.c (31)
-- Patch Links --
https://github.com/geany/geany/pull/2222.patchhttps://github.com/geany/geany/pull/2222.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/2222
It would be nice to be able to set key bindings for line operations, at least for sorting.
--
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/832
The Geany documentation describes the ctags pipe format file with clarity consequently I have been able to use it successfully. The documentation for the more important Tagmanager file format is much less clear:
_The Tagmanager format is a bit more complex and is used for files created by the geany -g command. There is one symbol per line. Different symbol attributes like the return value or the argument list are separated with different characters indicating the type of the following argument. This is the more complete and recommended tags file format._
Please tell me where I can find more complete documentation describing the tagmanager file layout?
--
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/2232
The poor contrast orange on white color scheme is, well, _poor_.
I spent five minutes trying to find some sort of dark theme, to no avail. Then I sadly clicked close, because it looks like this is just the thing for reviewing JSON documents.
Would be really great if there were some way to select a dark, minimal theme. Some of us are easily overstimulated ...
--
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/2237
I am for ever mistyping pairs of character I tried to write a transpose macro but I could not get it to work Is there a command to transpose the pair of letters on either side of the cursor? I see from the documentation that there is a transpose lines capability but I could not find anything about pairs of characters If there is not such a capability, please could you consider adding one as I would find it very useful <b>Thanks!</b>
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/814
Sharing parser code between Geany and u-ctags (= making ctags a library) is in progreass.
(The pull request for sharing was opened by @techee, and I merged them slowly.)
I, a head maintainer of u-ctags, must take care not breaking the interface between Geany and u-ctags when introducing a change to u-ctags.
I got a question about interface when an issue, https://github.com/universal-ctags/ctags/issues/2143, was opened.
Does adding a new kind to an existing parser of u-ctags impact on the interface and Geany behind the interface?
As far as I know, Geany converts u-ctags parser native-kinds to parser neutral abstracted kinds to use the result of u-ctags. Geany may have a table for the kinds conversion.
When I add a new kind to u-ctags, I guess the conversion table must be updated.
--
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/2227
Please consider making %F == "%d/%f" the representation for the full path and file name in the set build commands menu? Thanks!
--
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/2236
Please create an empty file, switch on line wrap mode and fill the first line until you are one character short of wrapping.
Duplicate this line
Now create a vertical cursor at the end of these lines using alt+shift+down covering both lines.
Add some more text to the end of these lines simultaneously to force wrapping to start on both of them.
Observe that the new text is placed on the the first and third lines rather than the second and fourth lines as might reasonably be expected?
--
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/2235
I have two identical tag files in my tags folder, one targeted at .pm files the
other at .xml.
diff -s Xml.pm.tags Xml.xml.tags
Files Xml.pm.tags and Xml.xml.tags are identical
If I edit zzz.pl tags work well:
geany -v zzz.pl
Geany-INFO: 18:15:46.169: Geany 1.32, en_US.UTF-8
Geany-INFO: 18:15:46.370: Loaded /home/phil/.config/geany/tags/Xml.pm.tags (Perl), 544 symbol(s).
If I start to edit an xml file:
Geany-INFO: 18:16:58.676: Loaded /home/phil/.config/geany/tags/Xml.xml.tags (XML), 0 symbol(s).
Now tag expansion no longer works either in the .pl file or in the .xml file.
Please suggest a way that I can get tag expansion to work in xml without
preventing it from working in .pl?
--
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/2231