@codebrainz: thanks. I will clean up everything and try again.
--
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/pull/620#issuecomment-335069374
https://github.com/geany/geany/pull/1633 fixes the majority of non-working
keybindings.
The ones that still don't work and should be changed are
```
GEANY_KEYS_EDITOR_AUTOCOMPLETE
GEANY_KEYS_SELECT_WORD
GEANY_KEYS_GOTO_LINE
GEANY_KEYS_GOTO_LINESTARTVISUAL
GEANY_KEYS_GOTO_LINEENDVISUAL
GEANY_KEYS
At the moment there's a problem with keybinding creation and processing.
When a keybinding is accessed using shift such as the zoom in keybinding
`Ctrl-+` which on English keyboard requires pressing `=`, the
`` key is preserved right now. This is visible when changing
keybindings - pressing the abo
Seems to work ok for me:
```bash
$ tree /opt/geany/lib
/opt/geany/lib
├── geany
│ ├── classbuilder.la
│ ├── classbuilder.so
│ ├── export.la
│ ├── export.so
│ ├── filebrowser.la
│ ├── filebrowser.so
│ ├── htmlchars.la
│ ├── htmlchars.so
│ ├── saveactions.la
│ ├── saveactions.so
@LarsGit223 not sure, Geany shouldn't be looking for plugins in `$(libdir)`
directly, and that's where the library should end up (tha'ts what the
`lib_LTLIBRARIES` change in my PR does). If the library is getting installed
into where Geany looks for plugins (ex. `/usr/local/lib/geany`) then that
Snippets are very useful and a marvelous way of improving productivity. Some
times I want to fill out a snippet in duplicate. Thus for instance, my snippet
`L`
expands to:
`L=L< %cursor% | /%cursor%-help >`
and I then type twice to get:
` L`
But what I would really like to do is have a
@codebrainz: thanks, at least linking works now.
But something is wrong regarding the lib path. After starting geany I see the
following error in the debug messages:
```
21:53:54: Geany INFO: Can't load plugin: libgeanypluginutils.so.0:
cannot open shared object file: No such file or
@LarsGit223 pushed 2 commits.
d36f70b Fix building of common utility library
b083090 Merge pull request #1 from codebrainz/commonlib-autotools
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://github.com/geany/geany-plugins/pull/620/files/b9e22446
> Yes, one can copy the contents of the terminal to the clipboard
It's confusing in this context to keep calling it "terminal" as that means a
completely different part of Geany's UI (the "Terminal" tab, containing an
actual terminal emulator). This is why I changed the title/description.
> we
Added https://github.com/LarsGit223/geany-plugins/pull/1 to improve build
system support.
--
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/pull/620#issuecomment-335028517
For instance after the following run:
`makeWithPerl --perl --run "Doc.pm" (in directory:
/home/phil/z/perl/cpan/JavaDoc/lib/Java)`
` 18 lines of documentation written to:`
` /home/phil/z/java/documentation.html`
` Compilation finished successfully.`
It would be very helpful to be able to clic
@Skif-off pushed 1 commit.
d395266 Add line: style as all other "case"
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://github.com/geany/geany/pull/1017/files/3398e3ebcec796d545fc808eb257df4f8f966cac..d3952660abfc69c2797be76dd2a64200f339c7ec
I am actually struggling with the makefiles. I get the following error message:
```
.libs/workbench_la-wb_project.o: In function `wb_project_dir_rescan_int':
/home/lars/DokuWiki/repos/geany-plugins/workbench/src/wb_project.c:586:
undefined reference to `filelist_scan_directory'
collect2: error: ld
This PR is a "visibility" PR to let people know that I am working on a common
utils lib for geany-plugins.
Right now this only includes a function for scanning a directory for files.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/620
After some discussion of alternatives, the simplest way for Textadept was to
add a local patch that undoes the block cursor selection change that happened
earlier this year:
https://foicica.com/lists/code/201710/4061.html
In case you'd like to do the same, I've made PR #1608 to first bring your
@Skif-off pushed 1 commit.
3398e3e Fix indentation
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://github.com/geany/geany/pull/1017/files/ca3205680e21ec0048bb7f57b9915a8cc8f2576f..3398e3ebcec796d545fc808eb257df4f8f966cac
eht16 approved this pull request.
Looks fine now.
If you don't mind, it would be cool to squash the commits together (maybe the
first three and keep the last one seperate or alltogether, as you like).
--
You are receiving this because you are subscribed to this thread.
Reply to this email dir
Merged #617.
--
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/pull/617#event-1283152333
@LarsGit223 you could just create a branch on your fork, probably make a PR for
visibility. Anyone can make a PR to your fork to integrate changes into the
main PR.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://gi
As a start I could try to move the directory scanning code of the workbench
plugin into such a lib. I think scanning directories for files based on a
pattern could be useful for other plugins to.
I guess we should create a branch for this. So I can move the code there and
who ever knows the bui
I agree to both of you.
@elextr: of course everything should be on an voluntary basis. If a developer
does not want to share the code then ok we have to accept it. It might also be
a matter of time to write code in that way that it can be commonly used. But
also like @codebrainz mentioned I wou
The same people who maintain Geany and Geany-Plugins (ie. contributors). It's
not some general purpose 3rd party library like GTK, it would be inside GP
repository for the specific purpose of providing shared functionality needed by
plugins and maintained by plugin developers and other contribut
So who controls the shared library, one thing programmers don't agree on is
which way libraries should/should not evolve eg Gnome vs the rest of GTK users.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/
Meh, one thing all developers can agree on is DRY :)
--
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/619#issuecomment-334993516
@LarsGit223 note also that plugins are created and maintained by different
people, they may not _want_ to share code. So you will have to address the
social as well as technical issues.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it
@LarsGit223 it's a chicken vs egg scenario. Until somebody has a need for such
shared code, nobody's going to integrate that into Geany-Plugins. Making an
empty library would be rather pointless. If you feel like extracting some
shared code, I could probably assist in integrating it into the bui
Ok, sounds like the simplest solution. I do not know when I will implement the
keybinding wizard.
Apart from that it should be considered to plan a common lib anyway. So plugin
developers can move common code there. If there is no possibility to do it,
then no one will start preventing this kin
A rather simple/clean solution would be to just put a tooltip column that says
something like:
```
Click to edit, blah blah blah.
Current shortcut: {translated name}
Default shortcut: {translated name}
```
Or something like that. It's not intrusive in the UI and adds value even for
Anglos.
An ASCII art representation:
```
+-+
| GTK |
+-+
^
|
+---+ +--++--++---+
| Geany |>| LibGeany |<---| Your Lib |
> I meant the library would NOT register itself as a plugin, right?
Correct, it would simply link against `libgeany.so` to gain access to the
plugin API.
> How intelligent is the runtime linker? I guess it simply links together every
> function that is in use. I mean if a plugin would use a fun
I am not sure its worth it though, the keyname is just a programming language,
and Geany is targetted at programmers after all.
--
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/1630#issue
Sounds like the concept with the invisible column is not working/would not
work. So the two-column concept would be kind of a possible workaround.
--
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/gean
I think I was unprecise. I meant the library would NOT register itself as a
plugin, right?
How intelligent is the runtime linker? I guess it simply links together every
function that is in use. I mean if a plugin would use a function of my library
then the function would be linked in even if th
@LarsGit223 the library could make use of the plugin API. It would just contain
the shared code that multiple plugins would want to use. This just puts the
burden of dependencies on the OS runtime linker instead of Geany's simplistic
plugin loader.
--
You are receiving this because you are sub
34 matches
Mail list logo
