The lua script solve the issue. But I would like to ask how the developers think about this now. Love Geany good 'old open source simplicity and customizability but this only issue prevented me of this discovery for years passing from one text editor to the next. Less distraction is esencial for me.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/633#issuecomment-1151739681
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/633/1151739681(a)github.com>
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2220
-- Commit Summary --
* Replace search dialog with search bar
-- File Changes --
M src/callbacks.c (2)
M src/editor.c (6)
M src/keybindings.c (5)
M src/notebook.c (290)
M src/search.c (24)
M src/search.h (6)
M src/ui_utils.c (31)
M src/ui_utils.h (4)
-- Patch Links --
https://github.com/geany/geany/pull/2220.patchhttps://github.com/geany/geany/pull/2220.diff
--
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/pull/2220
Geany version: 1.36
Gtk version 2.24.32
Glib version 2.60.6
Platform: Windows 10
Geany installed into: c:/Program Files (x86)/Geany/data
Interface language: Geman
What I did to set the cursor colour:
Using the Geany menu Werkzeuge/Konfigurationsdateien, I selected filetypes.common.
I located all lines starting with
`caret=`
I changed the first one to
`caret=0x3C3505;;true`
and I commented out the second one using a `#`, to make sure that these settings don't interfere.
`#caret=0x000000;0x000000;false;`
Using the menu Datei/Eigenschaften, I verified that the modifed filetypes.common refers to
`C:\Users\fisrona\AppData\Roaming\geany\filedefs\filetypes.common`
I terminated Geany and verified, that this file indeed contains my modifications.
I started Geany again, but the cursor colour is still black.
Of course there is still the original definition file in the installation directory,
`C:\Program Files (x86)\Geany\data\filedefs\filetypes.common`.
My guess is that Geany, erroneously, does not pick up the settings from my custom filetypes.common, but always the defaults from its installation directory. I don't want to edit the settings in `C:\Program Files (x86)\Geany`, because they would be overwritten everytime I update Geany to a new version.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3217
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3217(a)github.com>
Continuation of geany#259 since I can't push to @scriptum branch (I suggest you allow that).
I added some cleanup commits on top of @scriptum work and rebased onto 1.33.
@elextr @b4n Please give feedback (considering the history in geany#259). I think I'll merge this in maybe 10 days or so.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1813
-- Commit Summary --
* Add sidebar tree
* Add documentation for document list
* sidebar: optimized documents_sort_func() a bit
* sidebar: refactor get_doc_parent()
* sidebar: various minor changes
-- File Changes --
M doc/geany.txt (29)
A doc/images/sidebar_documents_only.png (0)
A doc/images/sidebar_show_paths.png (0)
A doc/images/sidebar_show_tree.png (0)
M src/sidebar.c (571)
M src/utils.c (2)
M src/utils.h (2)
-- Patch Links --
https://github.com/geany/geany/pull/1813.patchhttps://github.com/geany/geany/pull/1813.diff
--
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/pull/1813
Closed #259 via 6dcdefc18547ee5ce4a56f78caa316689d86b309.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/259#event-6769534315
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/259/issue_event/6769534315(a)github.com>
The debugger plugin closes the debugging section if you try to do a [Step in] to any **glibc** sys function.
**GDB** throws an exception with "No such file or directory." and the debugging section is then stopped or closed.
We need a way to pass to the debugger plugin where the source code of **glibc** is, so no exception is raised.
**Example:**
```
GNU gdb (Ubuntu 8.1.1-0ubuntu1) 8.1.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./minicom...done.
(gdb) b 77
Breakpoint 1 at 0x5365: file minicom.c, line 77.
(gdb) s
The program is not being run.
(gdb) run
Starting program: /apps/minicom-2.7.1/debian/minicom/usr/bin/minicom -D /dev/ttyUSB1
Lockfile is stale. Overriding it..
Breakpoint 1, port_init () at minicom.c:77
77 m_setparms(portfd, P_BAUDRATE, P_PARITY, P_BITS, P_STOPB,
(gdb) s
78 P_HASRTS[0] == 'Y', P_HASXON[0] == 'Y');
(gdb) s
77 m_setparms(portfd, P_BAUDRATE, P_PARITY, P_BITS, P_STOPB,
(gdb) s
m_setparms (fd=3, baudr=0x5555557866e0 <mpars+4032> "1500000",
par=0x555555786800 <mpars+4320> "N", bits=0x555555786770 <mpars+4176> "8",
stopb=0x555555786890 <mpars+4464> "1", hwf=1, swf=0) at sysdep1.c:396
396 {
(gdb) s
397 int spd = -1;
(gdb) s
399 int bit = bits[0];
(gdb) s
408 if (portfd_is_socket)
(gdb) s
413 tcgetattr(fd, &tty);
(gdb) s
__GI___tcgetattr (fd=3, termios_p=0x7fffffffde30)
at ../sysdeps/unix/sysv/linux/tcgetattr.c:34
34 ../sysdeps/unix/sysv/linux/tcgetattr.c: No such file or directory.
(gdb) s
38 in ../sysdeps/unix/sysv/linux/tcgetattr.c
(gdb) s
34 in ../sysdeps/unix/sysv/linux/tcgetattr.c
(gdb) s
38 in ../sysdeps/unix/sysv/linux/tcgetattr.c
(gdb) s
40 in ../sysdeps/unix/sysv/linux/tcgetattr.c
(gdb) s
46 in ../sysdeps/unix/sysv/linux/tcgetattr.c
(gdb) s
63 in ../sysdeps/unix/sysv/linux/tcgetattr.c
(gdb) s
42 in ../sysdeps/unix/sysv/linux/tcgetattr.c
(gdb) s
63 in ../sysdeps/unix/sysv/linux/tcgetattr.c
(gdb) s
42 in ../sysdeps/unix/sysv/linux/tcgetattr.c
(gdb) n
Warning:
Cannot insert breakpoint 0.
Cannot access memory at address 0x1ec4635941ad2a3e
__longjmp () at ../sysdeps/x86_64/__longjmp.S:45
45 ../sysdeps/x86_64/__longjmp.S: No such file or directory.
(gdb)
```
With **GDB** you can pass a parameter informing where to search for glibc source code, here is how:
_-d "directory to search"_
**sudo gdb -d /apps/libc6/glibc-2.27/stamp-dir --args ./minicom -D /dev/ttyUSB1**
```
GNU gdb (Ubuntu 8.1.1-0ubuntu1) 8.1.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./minicom...done.
(gdb) show directories
Source directories searched: /apps/libc6/glibc-2.27/stamp-dir:$cdir:$cwd
(gdb) b 77
Breakpoint 1 at 0x5365: file minicom.c, line 77.
(gdb) run
Starting program: /apps/minicom-2.7.1/debian/minicom/usr/bin/minicom -D /dev/ttyUSB1
Lockfile is stale. Overriding it..
Breakpoint 1, port_init () at minicom.c:77
77 m_setparms(portfd, P_BAUDRATE, P_PARITY, P_BITS, P_STOPB,
(gdb) s
78 P_HASRTS[0] == 'Y', P_HASXON[0] == 'Y');
(gdb) s
77 m_setparms(portfd, P_BAUDRATE, P_PARITY, P_BITS, P_STOPB,
(gdb) s
m_setparms (fd=3, baudr=0x5555557866e0 <mpars+4032> "1500000",
par=0x555555786800 <mpars+4320> "N", bits=0x555555786770 <mpars+4176> "8",
stopb=0x555555786890 <mpars+4464> "1", hwf=1, swf=0) at sysdep1.c:396
396 {
(gdb) s
397 int spd = -1;
(gdb) s
399 int bit = bits[0];
(gdb) s
408 if (portfd_is_socket)
(gdb) s
413 tcgetattr(fd, &tty);
(gdb) s
__GI___tcgetattr (fd=3, termios_p=0x7fffffffde10)
at ../sysdeps/unix/sysv/linux/tcgetattr.c:34
34 {
(gdb) s
38 retval = INLINE_SYSCALL (ioctl, 3, fd, TCGETS, &k_termios);
(gdb) s
34 {
(gdb) info source
Current source file is ../sysdeps/unix/sysv/linux/tcgetattr.c
Compilation directory is /build/glibc-CVJwZb/glibc-2.27/termios
Located in /apps/libc6/glibc-2.27/sysdeps/unix/sysv/linux/tcgetattr.c
Contains 80 lines.
Source language is c.
Producer is GNU C11 7.5.0 -mtune=generic -march=x86-64 -g -O2 -O3 -std=gnu11 -fgnu89-inline -fmerge-all-constants -frounding-math -fstack-protector-strong -fPIC -ftls-model=initial-exec -fstack-protector-strong.
Compiled with DWARF 2 debugging format.
Does not include preprocessor macro info.
(gdb)
```
I think there must be a way to tell **the debugger plugin** to pass the directory to search, so the debugging section is not closed.
I am still searching if is not possible to export a variable previous to debug with Geany to bypass the error.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1179
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/issues/1179(a)github.com>
Dear all,
I am very thankful to the debugger plugin team. It is a very good tool to my work.
I would like to ask some "how to" here. Maybe some of them can be considered into wishlist.
1. How to show variables' address?
In F90, we have LOC(x) to show its address in memery. Can I use it in the "watching window" as well?
2.how to access some variables that are located under module?
In intel f90+VS in Windows10, we have "mod::" method in debugger to enable this. Can we have the similar functions in geany?
3. ... (Maybe we can add more "enhancement" under this box?:D)
Thanks.
Shuo
--
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/583
It would be a great addition to Debugger plugin to have possibility to see disassembly view of debugged program/C file :)
Capstone as a disassembler is worth to look into considering this issue to be resolved IMHO:
http://www.capstone-engine.org
--
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/1038
This should fix #1164 , and replaces #1165.
BEWARE: I did NOT test this with libgit2 1.4, that I don't have yet. I might go to the trouble of building it and all, but for now this is a theoretical PR, but if libgit2 1.4 users can verify it it'd be great.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/1177
-- Commit Summary --
* git-changebar: Simplify libgit2 version checks
* git-changebar: Add support for libgit2 1.4
-- File Changes --
M git-changebar/src/gcb-plugin.c (88)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/1177.patchhttps://github.com/geany/geany-plugins/pull/1177.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1177
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/pull/1177(a)github.com>