[Github-comments] Re: [geany/geany-osx] Open dialog enter file path text (#14)
You can simply use `Control + L` and it will show GTK's input for File Path -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-osx/issues/14#issuecomment-1987466005 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany] Set Build Commands Question - add debug flag (Discussion #3787)
Closed #3787 as resolved. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/discussions/3787 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany] Set Build Commands Question - add debug flag (Discussion #3787)
You are correct! It is working now. Thank you very much! -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/discussions/3787#discussioncomment-8739188 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany-plugins] Make updatechecker plugin for MacOS (Issue #1314)
Just to note what the expectation of many users may be, both Chrome browser and Vscode IDE update checkers indicate a new version in app, and when triggered to update can indicate if its available by an "alternate channel" which means the distro normal update mechanism rather than direct from Google/MS source repo. Don't know how they do that, but maybe its in the open source parts of those apps? -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/issues/1314#issuecomment-1987398619 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany] How to hide mouse cursor on Linux (Issue #3788)
AFAIK there is no such capability in Geany. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3788#issuecomment-1987387188 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany-plugins] Make updatechecker plugin for MacOS (Issue #1314)
> AFAIK Geany is not mainly distributed via some sort of repository like "brew" > or so but via downloadable installers from our website and so I thought the > update checker plugin would do the same job on Macos as on Windows. I thought I had seen @techee make bugfix builds on the geany-osx repository, I guess if they get uploaded to the Geany website that would be ok, but then whats their version, if its the same then the update checker won't notice? -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/issues/1314#issuecomment-1987385919 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany-plugins] Make updatechecker plugin for MacOS (Issue #1314)
> The update checker for Linux works incorrectly, it checks the Geany > repository for a new version, not the repositories for the current distro. > Most distros don't update versions of software like Geany on LTS versions for > example. So it just feeds frustration for users of such I'd say it depends on the user. There is maybe a minority of users who compile Geany themselves from release tarballs and for those the plugin might be useful. > Its really only useful for Windows, but maybe it could be made useful for > Macos if it looked at the right repository because it can get new bugfix > releases separate from Geany. Isn't the plugin for Macos in the same way useful as for Windows as it checks geany.org for the latest version and this is where the Macos version is distributed. AFAIK Geany is not mainly distributed via some sort of repository like "brew" or so but via downloadable installers from our website and so I thought the update checker plugin would do the same job on Macos as on Windows. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/issues/1314#issuecomment-1987320147 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany] Add CodeQL Analysis workflow (PR #3769)
> Adding ` workflow_dispatch:` might be a good idea to manually re-run the > workflow. I would still recommend this simple change. And it seems the configuration still has syntax errors: https://github.com/geany/geany/actions/runs/8135027731/workflow -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3769#issuecomment-1987318532 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany] Add CodeQL Analysis workflow (PR #3769)
@eht16 commented on this pull request. > @@ -8,6 +8,13 @@ on: push: branches: - master +- '**' I don't see why, at least for this case it seems a bit beyond the goal. If we have use cases for excluding files from triggering a CI run, we can add them but no excluding only two YAML files doesn't change much. Without having checked it, I think about 95% of the commits will change files which should trigger the CI anyway, so don't waste resources maintaining an articial exclude list. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3769#discussion_r1518925242 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany] Set Build Commands Question - add debug flag (Discussion #3787)
To include debug info in the executable I think -g needs to be applied to the link stage as well as the compile stage. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/discussions/3787#discussioncomment-8736700 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] [geany/geany] Set Build Commands Question - add debug flag (Discussion #3787)
I've been using Geany for a few days and have run into an issue that I'm unable to resolve. I've created a test project and created a c application and compiled and linked it successfully. I then decided to turn on debug flag and try out the Debug Plug-in. I updated the compiler from **gcc -Wall -c "%f"** to **gcc -g -Wall -c "%f"** in both the Project Properties and the Set Build Commands windows. After deleting the object and executable files, I compiled and linked successfully. However, the Debug Plug-in didn't work. To troubleshoot, I ran gdb in a terminal and noticed that the debug symbol information for my test application was missing. After discovering this, I deleted the object and executable files and recompiled on the command line with the debug flag set (in the Geany folder). After doing this gdb worked fine and I was able to run the Debug Plug-in within Geany. It seems that the compiler flag I added to the property windows in Geany is not being picked up. Note that the compiler message in the Compiler message window indicates that it is. Any recommendation on what I may be missing/doing incorrectly? Thanks. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/discussions/3787 You are receiving this because you are subscribed to this thread. Message ID:
