After spending a lot of time on things like tag manager where nobody sees any difference, I got quite a radical idea that it would be nice to start working on things that somebody wants ;-). Assuming that "thumbs up" is a good proxy to "I want this", this translates to:
<img width="765" alt="Screenshot 2024-08-23 at 12 33 41" src="https://github.com/user-attachments/assets/258915a2-b32d-4782-bbe4-e3942dcc…">
I think we are actually in a very good position to address most of these in the next release(s). This meta-issue tries to summarize where we are if we try to address these issues:
- [ ] #905 - pretty much addressed by @LiquidCake's #3911 - the discussion in the issue also mentioned things like hot exit but what the OP asked for was really the Notepad++ feature automatically saving/restoring untitled documents.
- [ ] #2184 - hopefully there - have to test a few more things (https://github.com/techee/geany-lsp)
- [ ] #2750 - I asked Neil for increasing it so it's 60 (up from the previous 20) which is reasonably "unlimited". Will be fixed once we update Scintilla.
- [ ] #1141 - addressed by #3899 (the feature itself is in Scintilla itself, we just have to make the click-modifiers configurable as depending on the desktop, some configurations work and some not)
- [ ] #1268 - fixed by #3934
- [ ] #872 - I guess most users wanted it for editor tabs which is fixed already but there is also Nick's #3469 that could be applied for the sidebar and message window
- [ ] #1192 - no work-in-progress-yet. The only issue here is that the popup window is shown using `dialogs_show_question_full()` which is used by other popups with possibly destructive actions where default "Cancel" is the right choice. So either this function has to take an extra parameter specifying which of the buttons should be default or to create a new dialog specifically for this situation.
- [ ] #371 - see https://github.com/ScintillaOrg/lexilla/pull/265 which I eventually port for Geany
- [ ] #3724 - slightly lower in the thumbs up list but I think it would also be nice to add, see https://github.com/ScintillaOrg/lexilla/pull/267
Fear not, I'm not adding #2061 to this list :-).
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3938
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3938(a)github.com>
Standard gettext should be used over glib's glue these days.
AM_GLIB_GNU_GETTEXT and glib-gettextize are deprecated. This helps
possible meson build (no concrete plans yet) as well as working with
intltool is harder over there. gettext, on the other hand, is supported
out of the box in meson.
Beware, autopoint is a new dependency when building from git,
should not affect tarballs. Also, it's already required by Geany core.
Additionally, autogen.sh follows Geany's autogen.sh more closely,
allowing for out-of-tree builds.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/1183
-- Commit Summary --
* Use standard gettext, following Geany core.
* Fix issues found by standard gettext
* Update po files after gettext transition.
-- File Changes --
M .github/workflows/build.yml (1)
M .gitignore (7)
M autogen.sh (11)
M build/common.m4 (1)
M build/i18n.m4 (10)
M configure.ac (8)
A po/LINGUAS (1)
A po/Makevars (82)
M po/POTFILES.in (8)
M po/be.po (710)
M po/ca.po (771)
M po/da.po (697)
M po/de.po (966)
M po/el.po (690)
M po/es.po (952)
M po/fr.po (950)
M po/gl.po (780)
M po/it.po (847)
M po/ja.po (770)
M po/kk.po (720)
M po/nl.po (812)
M po/pt.po (0)
M po/pt_BR.po (0)
M po/ru.po (0)
M po/tr.po (0)
M po/uk.po (0)
M po/zh_CN.po (0)
M treebrowser/src/treebrowser.c (0)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/1183.patchhttps://github.com/geany/geany-plugins/pull/1183.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1183
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/pull/1183(a)github.com>
I use geany for python programming with vte enabled. I regularly use `Send Selection to Terminal` for my work and I find it most helpul for debugging my code. `Send Selection to Terminal` works every time except the Indented lines (eg:`<tab>print('world')`) where it result in an `IndentationError`. I also request a function in which we can send a line of code to terminal without even selecting it. For example
```
i=0
print("hello")
if i==0:
print("world")
```
if I want to print hello, now I need to select the line `print("hello")` and then `Send Selection to Terminal` to get the output in vte. Instead of this I want to click any where on that line and then do `Send Line to Terminal` without selecting it. Similarly to print world instead of selecting `<tab>print('world')` I want to click on that line and then print the output world.
--
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/2174
I tried to code a plugin for copilot but soon realized that your api doesn't allow low level control of scintilla or I'm too noob to realize how. Copilot only needs to grab context from current cursor position (say 200 chars before and after), then it will suggest autocompletion options. Btw, Copilot is not the only tool for the task, I plan to add and OpenAI backend that can be gracefully replaced by LocalAI for 100% private and off-line coding (so no IP issues). Devs can choose to train/finetune their own LLM if they wish, plug it into LocalAI and let the geany plugin take care of the rest.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3543
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3543(a)github.com>
So I recently decided to abandon my old gtk2-based editor after some +15 years,
largely because I can no longer compile gtk2 from source, for reasons related
to the glib stack (something has been deprecated and I don't know the workaround,
but I can no longer wait for anyone upstream patching gtk2, so I now took the
full dive finally).
I toyed with the idea of sublime, but I think I am less likely to adjust sublime towards
behaviour I am quite use, as opposed to geany, which is open source. So I'll give
geany a more serious try this time. I used it in the past, e. g. for C++ files, but not
yet for all files. Right now I am using geany for ALL files.
There are many small issues but I don't want to spam the issue tracker with tons
of ideas that are possibly only for my own use case. Nonetheless I hope to be
able to convince the geany devs towards more flexibility in general, via options
and preferences we could toggle as-is. Geany already supports quite many
options, so I hope we can support even more options - if they make sense.
Alright - now to the issue here.
First, have a look at this screenshot:
https://i.imgur.com/mWzOafF.png
You can see the open files. Evidently I am currently modifying a german exam
question test for evolution of hominids / hominidae :D - the key issue, though,
is the pop-up widget that shows the opened files.
The currently selected file is shown in bold - that is nice.
However had, often I can not tell WHERE the files are. Some may be same-named
or similarly-named, so I would like to also have the option to show the full path
right there (left-padded, e. g. all are aligned towards the left-side, but on the
right side we may allow overflow; the full widget width would thus be determined
by the file with the longest name.)
I am very much used to that behaviour from my old editor, where I can see the
full path at all times.
So, my issue request would be for geany to add an option to show the FULL
path instead, rather than the truncated path (in ruby, the filename itself
would be obtained via File.basename(), so instead I would be looking for
File.absolute_path() - not sure how C does this but perhaps gtk has some
method that shows the full path).
In the option dialogue, we would then have to add a new entry at
**Preferences -> Files**; perhaps call it, as a check-button, "Show full
path of files". This would NOT be the default, so everyone could enjoy
the current behaviour of geany, rather than adjust to the one proposed
in this issue request.
As for a more objective rationale for this feature: we would instantly
know where the file resides at. (Actually, my old editor not only made
the current file bold, but used different colours too. But I am perfectly
fine without colours here too, I just need the feature that I know the
full path at all times, as this is less confusing to me than merely the
short-filename itself as such.)
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3800
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3800(a)github.com>
There is a custom file type syntax highlighter for Objeck here:
https://github.com/objeck/objeck-lang/tree/master/docs/syntax/geany
But there is no official lexilla lexer yet. There is an open FR on lexilla's repo:
https://github.com/ScintillaOrg/lexilla/issues/121
The OP summed the problem with the custom file type syntax highlighter pretty well. But he is wrong about the similarity between Objeck and C/C++. They are both curly braces languages but they are not really similar. I think Objeck needs its own lexer.
I don't know which languages most resemble Objeck, but using the C ctags parser for Objeck seems to not work well, too.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3963
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3963(a)github.com>
**Conditions**
- enable the sidebar
- in the sidebar: enable the tab with the title `Symbols` and the tab with the title `Documents`
- turn off all plugins, to be sure that the issue has not something to do with plugins
- open some documents in Geany
**Steps to reproduce**
1. click in the editor
2. click in the sidebar on the tab-title `Documents`
3. with the mouse: mark the first item from the top (result: the first item is marked)
4. click in the editor
5. click in the sidebar on the tab-title `Symbols`
6. click in the sidebar on the tab-title `Documents`
7. press 1x the arrow-down key on the keyboard (result: the next item is marked; so, that means that the release of a click on the tab-title after 6 made the content-area of the tab in focus)
8. click in the editor
9. click in the sidebar on the tab-title `Documents`
10. press 1x the arrow-down key on the keyboard
**Expectation**
the next item should be marked
**Result**
nothing visible happens; that means that the release of a click on the tab-title in 9 didn't make the content-area of the tab in focus; so, the behavior after 6 is not the same behavior like after 9; but there is something that happens even if it is not visible: after having pressed 1x the arrow-down key on the keyboard in 10, the focus moves from the tab-border to the content-area because if one press again 1x the arrow-down key on the keyboard, then the next item is marked; see also "Remark I" down below
**Remark I**
in 3: instead of the first entry, mark the last entry; then do 4 to 6; then in 7 press 1x the arrow-up key instead of the arrow-down key on the keyboard to mark the item before the last item; then do 8 and 9; then in 10 press 1x or several times the arrow-up key instead of the arrow-down key on the keyboard; there will be no change; one have to press first 1x the arrow-down key (!!) on the keyboard to move the focus from the tab-border to the content-area; then press 1x the arrow-up key on the keyboard to mark the second last item
**Remark II**
one can do "Steps to reproduce", but without 8
**Remark III**
in "Steps to reproduce" one need first to click in the editor, then on the tab-tile "Symbols" and then on the tab-title "Documents", so that the release of the click on the tab-title will put the content-area of the tab in focus; but there is also a second possibility to put the content-area of the tab in focus: if the tab-title "Symbols" is active while the editor has focus, and then if one click on the tab-title "Documents"
**History**
I reported the issue already in the year 2021 on the website of the plugin `Preview` (https://github.com/xiota/geany-preview/issues/15) because to that time I thought that the plugin `Preview` was the problem. But today I could reproduce the issue while all plugins were deactivated. That means that not the plugin `Preview` is the problem, but Geany.
**System**
Lubuntu 24.04
Geany 2.0
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3961
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3961(a)github.com>
Without overview geany does not crash... when overview is enabled creating a new file in Linux X11 causes geany to crash when the file is clicked. Windows and wayland seem to be unaffected. See bug https://github.com/geany/geany/issues/2736
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1354
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/issues/1354(a)github.com>
I had a Thunar(file manager) that lets you make custom actions on whatever file is highlighted.
I had a custom action meant to only open text files using Geany.
I accidentally click on a 3.9 Gb .iso file. :slight_smile:
Using Mate System Monitor, I saw that my action caused the resources to get to around 80% when I did a reboot.
I wonder if Geany could be written so it checks first if it is a text file?
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/3965
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/repo-discussions/3965(a)github.com>