Is it possible? I set up my favorite color scheme for the editor, but the rest of UI is very bright "black-on-white".
--
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/2928
After starting geany 1.37.1 Debian GNU/Linux 10 (buster) with a markdown-file that was opened already yesterday, the preview is not working (see below) until the moment I edit the file again. Phew, quite difficult to explain exactly, sorry.
The shown 'error' in the preview is: _The current document does not have a Markdown filetype_
Not a big issue for me but I still wanted to post 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-plugins/issues/1062
It would be convenient to append items "copy filename" and "copy filepath" on tabs right click menu
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/868
I have noticed that the colors for the message window (comprising status, compiler, messages, scribble and terminal) are hard-coded.
I think it is possible to do some basic calculations to detect light and dark themes and set the colors for the messages accordingly.
I will be trying to fix this issue.
--
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/2644
In the Documentation generator menu the manual links to ```/usr/share/doc/geany-plugins/geanygendoc/html/manual.html``` and not ```/usr/share/doc/geany-plugin-gendoc/manual.html```.
This is in Geany 1.33-1 on Debian 10 (buster) in XFCE 4.12.5.
--
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/992
In `Edit=>Preferences=>Editor.Features`, I added a checkbox "Comment Blank Line(s)" for issue #2239.
When this option is turned on and when commenting (`Edit=>Format=>Comment Line(s)`) or toggling comments (`Ctrl+E`), blank (empty) line(s) will also be commented.
For example, if you comment this code...
```Ruby
puts <<EOD
EOD
```
..., it will do this:
```Ruby
# puts <<EOD
#
# EOD
```
It should work for Comment, Uncomment, and Toggle. By default, it is off/false.
If this merge is accepted, `doc/geany.html` and the screenshot in this HTML file will need to be updated.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2452
-- Commit Summary --
* Add "Comment Blank Line(s)" option
-- File Changes --
M data/geany.glade (20)
M doc/geany.txt (11)
M src/callbacks.c (2)
M src/editor.c (2)
M src/editor.h (1)
M src/keyfile.c (2)
M src/prefs.c (6)
-- Patch Links --
https://github.com/geany/geany/pull/2452.patchhttps://github.com/geany/geany/pull/2452.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/2452
TOML is a fairly strictly defined configuration file syntax, used by various projects, supported by plenty of languages and already supported by some editors. I'm not familar with geany plugin dev (and lacking the time anyway) but maybe someone's interested in creating a syntax highlighting ruleset, similar to the INI config format.
https://github.com/toml-lang/toml
--
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/1268
Hello!
I had totally forgot that Geany is available for Mac. The small issue which I am facing is that the "open file" dialog does not show me a native file opener dialog. The reason I want the native file opener dialog is that I have bookmarked a lot of things in Finder and I have to dig into a lot of folders to find the folder I want to open with Geany.
Plus, nice work! I was introduced to Geany few years ago, and this being an IDE takes less RAM + battery than normal text editors 👍
--
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/1310
This pull request aims to be a complete support for systems without gvfs-fuse or fuse installed. It supersedes #963 (I'm creating a new pull request because there are some changes to the used approach, not just addressing issues from the original pull request).
The main changes of this pull request compared to #963 are:
1. More fine-grained approach to GIO usage - previously I for instance replaced all g_file_test() usages with GIO (depending on the configuration) but now it's done only for files which can possibly be remote (i.e. not for config files etc.). If not remote, g_file_...() is still used.
2. Got less crazy about USE_GIO_FILE_OPERATIONS Geany configuration and use this one only when opening/closing documents is involved in the IO. This is when things can go wrong when mixing IO methods. But for other things there's no need to maintain both g_file_...() implementation and GIO implementation and only one of them is used (depending on whether the file can be remote).
3. There's no new plugin API - basically I think plugins don't need to know the value of USE_GIO_FILE_OPERATIONS as they aren't involved in opening/closing documents. If a plugin wants to support remote files, it should use GIO. All existing API functions that could possibly involve file IO have been converted to use GIO. It's not completely black and white as some functions are also used by Geany for opening documents so these still test the USE_GIO_FILE_OPERATIONS value. Not having the file IO functions in the API leads to some duplication of code in plugins but it's not that bad and probably better than adding more and more utility functions to the API.
4. It now works not only when gvfs-fuse is uninstalled, but also when fuse is uninstalled. I was still getting the remote location mounted before I uninstalled fuse and discovered more problems on the way. I recommend testing with fuse uninstalled.
5. Some things like file properties of remote files, TM or saveactions support were missing in the previous pull request. Everything should work now.
6. TM works only for parsing edited file's buffers - there's no support for parsing remote files (we'd have to change ctags for this). I think this is OK as loading complete projects over network could take ages and everything would be frozen as we use blocking GIO. For the same reason I don't plan support for remote projects in my projectorganizer plugin. I haven't really checked how other plugins behave but I don't expect big problems. doc->file_name and doc->real_path can now be URI and if plugins do some reasonable error checking, there should be no problem and they should fail gracefully if they don't use GIO. (I haven't checked but IMO plugins shouldn't read/write doc->file_name as this would interfere with the opened buffer in Geany. Most of the checks I've seen were like if (doc->file_name != NULL) {...}).
7. I didn't get too crazy about saveactions plugin GIO support - it now only supports saving backups into a local directory and not to a remote one. I think nobody will really use remote URI as a location for backups - it would be rather impractical and slow. But can easily add this if someone thinks the opposite.
Apart from the minor limitations I mentioned, I'm not aware of anything missing - I believe this pull request ticks all checkboxes from #1145 with the exception of Windows support which I probably won't do myself and which can be done later independently of this pull request.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1414
-- Commit Summary --
* Replace g_file_test() with a GIO variant when needed
* Update utils_get_path_from_uri() to return URI when using GIO
* Keep URIs in utils_tidy_path()
* Use g_file_new_for_uri() when needed
* Don't create separate tagmanager library
* Preserve URIs in tm_get_real_path()
* Allow parsing remote files opened in the editor
* Merge implementations of write_data_to_disk() and utils_write_file()
* Use gtk_file_chooser_get_uri() in file opening/saving dialogs
* Add GIO version of document_rename_file()
* Use GIO in utils_get_file_list_full()
* Add file reading utils function
* Load project config files using the new utility function
* Remove unnecessary utils functions
* Use g_file_set_contents() instead of utils_write_file() for local files
* Use GIO in utils_mkdir()
* Add GIO implementation to utils_is_file_writable()
* Use GIO for filetypes_detect_from_file()
* Eliminate g_path_is_absolute() direct calls
* Use GIO for file properties dialog
* saveactions: Make backups work for remote files
* Document that document file_name and real_path can be URIs
-- File Changes --
M configure.ac (1)
M plugins/export.c (23)
M plugins/filebrowser.c (74)
M plugins/htmlchars.c (2)
M plugins/saveactions.c (108)
M src/Makefile.am (25)
M src/callbacks.c (10)
M src/dialogs.c (78)
M src/document.c (137)
M src/document.h (4)
M src/filetypes.c (31)
M src/keybindings.c (8)
M src/keyfile.c (8)
M src/libmain.c (13)
M src/msgwindow.c (8)
M src/osx.c (2)
M src/project.c (74)
M src/sidebar.c (2)
M src/stash.c (3)
M src/symbols.c (1)
D src/tagmanager/Makefile.am (32)
M src/tagmanager/tm_source_file.c (54)
M src/tagmanager/tm_source_file.h (3)
M src/toolbar.c (2)
M src/ui_utils.c (8)
M src/utils.c (351)
M src/utils.h (24)
M src/win32.c (4)
-- Patch Links --
https://github.com/geany/geany/pull/1414.patchhttps://github.com/geany/geany/pull/1414.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/1414
By default, ctags generates scope information using
```
parent_kind:A::B::C
```
where `A::B::C` is the scope of the parent tag. This is a bit problematic when parsing such fields because we have to compare the `parent_kind` value against all valid kinds of the language and if it matches, it means that what follows is the scope. This slows down parsing of such tags and also requires that `parent_kind` is really a valid kind for the given languages.
ctags can also add extra "scope:" prefix to this field when using the sZ field specification option on the command line:
```
scope:parent_kind:A::B::C
```
This way, the scope field can be detected easily by comparing against "scope:" which speeds up parsing. Also, the parsing code doesn't care about the value behind "scope:" so "class" can be used also for languages that don't have the "class" kind.
I haven't regenerated the tag files to avoid a big diff but the result will add "scope:" for every tag's scope field and this should be done separately.
By the way, this could help anyone reviewing #3049 understand what's going on. Parsing scope fields with the `scope:` prefix happens here:
https://github.com/techee/geany/blob/f49b19f3bfe61cf7ae27075f28ec5bd7c570a1…
If scope is not obtained this way, the code tries to go through all the fields which weren't parsed before and check if they start with a kind name of that language. If they do, the field is considered to be scope, see:
https://github.com/techee/geany/blob/f49b19f3bfe61cf7ae27075f28ec5bd7c570a1…
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3592
-- Commit Summary --
* Prefix generated scope field by the "scope:" prefix
-- File Changes --
M scripts/create_tags_helper.py (6)
-- Patch Links --
https://github.com/geany/geany/pull/3592.patchhttps://github.com/geany/geany/pull/3592.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3592
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3592(a)github.com>