> PRs are welcome, note that plugins are maintained by individuals, the time
> and energy they have to devote to the plugin may be limited.
I'd be more than welcome to help with these topics if someone could guide me
with the first steps to get into it.
--
Reply to this email directly or view
See
[comment](https://github.com/geany/geany-plugins/issues/1226#issuecomment-1449089155)
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1227#issuecomment-1449090068
You are receiving this because you are subscribed to this thread.
Message
PRs are welcome, note that plugins are maintained by individuals, the time and
energy they have to devote to the plugin may be limited.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1226#issuecomment-1449089155
You are receiving this because
If the Geany filebrowser plugin is activated and if it has a method of setting
its directory that might be usable, but if you want to open an external
filebrowser that becomes a portability issue since its different between
Windows, OSX and just about each Linux desktop and some distros.
--
Sometimes it would be helpful, if there would be a feature to automatically
navigate the workspace to the currently opened file to not have to manually
browse through all the folders and files and look for where it is.
Either a configurable shortcut or a new button to sync the Workbench would be
Every time I start Geany, I have to open the Workbench file manually. A setting
to remember the last opened workspace and open it when Geany is started, would
be very helpful.
Also a list of recent workspaces (similar to the one already available for
projects) would be nice to have.
--
Reply
While using Geany, sometimes I need to open the location of a file or folder.
For that, it would be nice to have a context menu entry in the workbench to
open a folder browser at the location that file or folder is located at.
--
Reply to this email directly or view it on GitHub:
> I don't see this as a particularly bad
No, its not ...
> few specifics hard-coded for the languages we have to
... just that you can't do that ATM without a hard coded filetype. Which is
why I asked the question, not knowing that the parser was a freebie thrown in
by @techee, not added by
Agree with @eht16 that it does not fit with Geany core and its best as a plugin.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3382#issuecomment-1447898281
You are receiving this because you are subscribed to this thread.
Message ID:
> Oh ok, but having added a parser I wonder why the creator of the Typescript
> filetype didn't go the whole hog and make a built-in filetype. Then they
> could customise all the language dependent code scattered throughout Geany.
I don't see this as a particularly bad, actually if we could get
10 matches
Mail list logo
