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:
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:
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:
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
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:
> 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
> 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
> 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
@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
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
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
11 matches
Mail list logo
