Please document that automark uses the **marker_search** color.
--
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/492
Hi,
I like using geany, and i use a specific sidebar width to get a nice preview of my document using plugin-markdown. And i could'nt find a way to fix the sidebar width, so i have to adjust it manually at every startup...
Is it possible / easy / desirable to add a configuration option to fix the width of the sidebar ?
Thank you very much for your nice software !
--
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/1435
Environment is geany 1.27 on 64-bit Ubuntu 14.04
Confusion results when script.sh contains multi-line statements with some intervening lines commented out with #. Sample:
`statement start \`
`# statement continue \`
`statement final`
The 2nd and 3rd line both display in red.
Deleting the **\** on line 2 gives shows it red and line 3 black. I believe that's the correct result.
My intent is to activate / deactivate the 2nd line by removing / inserting the leading **#**
---
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/1153
With geany 1241 Pretty much any file, even if it has a maximum line length of 80 characters - the horizontal scroll bar is about 300 characters wide, so it's hard to tell if there's a very long line in the file without actually examining each line
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/886
When I was making the sources of our ctags use tabs-only indentation, I used Geany's "replace tabs with spaces" and "replace spaces with tabs". However, after using it I realized that every time I also had to set the document's indentation type manually which was a bit annoying and unnecessary. IMO when doing replacements of tabs<->spaces in the whole document, we should set also the document's indentation type to the new type. The first patch does this.
The second patch is just kind of cleanup which makes the implementation of undo() and redo() more similar to each other.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1161
-- Commit Summary --
* Set document indent type when replacing tabs<->spaces in the whole document
* Make UNDO_EOL/UNDO_INDENT always precede the attached Scintilla action
-- File Changes --
M src/document.c (64)
M src/documentprivate.h (1)
M src/editor.c (36)
-- Patch Links --
https://github.com/geany/geany/pull/1161.patchhttps://github.com/geany/geany/pull/1161.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/1161
I use Geany as a teaching tool for code, and the status window isn't all that useful for students. It would be really beneficial if the default message pane display was configurable, so we could choose to display the terminal by default.
--
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/1446
This is my naive attempt at solving #1136. It works for me (not heavily tested yet), but I’m not sure if it’s a good idea. I would appreciate any feedback.
Geany’s message window is sort of detached from the editor. In general, it’s just lines of text that are not parsed or associated with the files in question until the user wants to navigate to one of them (although there are some exceptions).
Constrained by this design, I bolted on a cache of line number shifts. Actually two caches: one for the messages tab (`line_shifts_msg`) and one for the compiler tab (`line_shifts_compiler`). A cache is cleared when the user initiates a search/build (`msgwindow_clear_tab`), and then updated whenever the user adds/deletes lines in *any* open file (`SCN_MODIFIED` with a non-zero `linesAdded`), as long as *any* messages/errors are present. A cache is a hash table where keys are filenames and values are sequences of “at line, lines added” pairs (`LineShift`).
This of course means some overhead on mundane editing operations. Line numbers are requested from Scintilla, filename hashes are computed, arrays may need to be resized. Some of this overhead could be optimized out, but I’m not sure it’s worth it.
Also, this approach doesn’t handle undo very well. If there’s a compiler error on line 3, and I delete that entire line, and then undo the deletion, navigating to that error will now bring me to line 2 instead of 3, because the undo is understood as inserting an unrelated new line.
A possibly cleaner and/or more efficient approach might be to rely on Scintilla’s features such as line markers or indicators. That would probably require some revamp of the message window: lines would have to be parsed eagerly and associated with those Scintilla features as long as the corresponding file is open. I haven’t tried that approach.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1481
-- Commit Summary --
* Track changes to line numbers for messages and compiler errors
-- File Changes --
M src/build.c (2)
M src/editor.c (26)
M src/msgwindow.c (130)
M src/msgwindow.h (4)
M src/search.c (4)
-- Patch Links --
https://github.com/geany/geany/pull/1481.patchhttps://github.com/geany/geany/pull/1481.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/1481
How-to:
* Start spell-checking a large document (I used a 4MB file that I can provide, if needed)
* Close said file while the spell-checking is still ongoing
* Geany crashes
Trace:
```
$ geany -v
...
SpellCheck-Message: Checking file "**redacted**" (using "en_US" (myspell)):
Errore di segmentazione
```
--
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/547
Segmentation fault when split window is used with some activity like editing. I am using the gtk3 build.
BackTrace:
```
Thread 1 "geany" received signal SIGSEGV, Segmentation fault.
0x00007ffff7a02eed in Document::MovePositionOutsideChar (this=0x651dd0, pos=291,
moveDir=1, checkLineEnd=false) at src/Document.cxx:628
628 if (pos >= Length())
#0 0x00007ffff7a02eed in Document::MovePositionOutsideChar (this=0x651dd0,
pos=291, moveDir=1, checkLineEnd=false) at src/Document.cxx:628
#1 0x00007ffff7a043bb in Document::CountCharacters (this=0x651dd0,
startPos=<optimized out>, endPos=292) at src/Document.cxx:1399
#2 0x00007ffff79e8938 in ScintillaGTKAccessible::Notify (this=0x2340610,
nt=0x7fffffffc620) at gtk/ScintillaGTKAccessible.cxx:866
#3 0x00007ffff79e8d47 in ScintillaGTKAccessible::SciNotify (
widget=<optimized out>, code=<optimized out>, nt=<optimized out>,
data=<optimized out>) at gtk/ScintillaGTKAccessible.h:33
#4 0x00007ffff55bbfa5 in g_closure_invoke ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#5 0x00007ffff55cdfc1 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#6 0x00007ffff55d6d5c in g_signal_emit_valist ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#7 0x00007ffff55d708f in g_signal_emit ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8 0x00007ffff79decdf in ScintillaGTK::NotifyParent (this=0x2cf24f0, scn=...)
at gtk/ScintillaGTK.cxx:1088
---Type <return> to continue, or q <return> to quit---
#9 0x00007ffff7a19aaa in Editor::NotifyModified (this=0x2cf24f0, mh=...)
at src/Editor.cxx:2713
#10 0x00007ffff7a058ae in Document::NotifyModified (this=this@entry=0x2cee530,
mh=...) at src/Document.cxx:2267
#11 0x00007ffff7a07540 in Document::DeleteChars (this=0x2cee530, pos=291, len=1)
at src/Document.cxx:1054
#12 0x00007ffff7a12cf7 in Editor::DelCharBack (this=0x35fce20,
allowLineStartDeletion=true) at src/Editor.cxx:2265
#13 0x00007ffff7a16a4a in Editor::KeyCommand (this=0x35fce20,
iMessage=<optimized out>) at src/Editor.cxx:3726
#14 0x00007ffff7a20126 in Editor::WndProc (this=0x35fce20, iMessage=2326,
wParam=0, lParam=0) at src/Editor.cxx:7478
#15 0x00007ffff79e48a6 in ScintillaGTK::WndProc (this=0x35fce20,
iMessage=<optimized out>, wParam=<optimized out>, lParam=0)
at gtk/ScintillaGTK.cxx:862
#16 0x00007ffff7a0e7af in Editor::KeyDownWithModifiers (this=0x35fce20, key=8,
modifiers=0, consumed=0x7fffffffcba7) at src/Editor.cxx:3842
#17 0x00007ffff79e1973 in ScintillaGTK::KeyThis (this=0x35fce20, event=0x360c370)
---Type <return> to continue, or q <return> to quit---
at gtk/ScintillaGTK.cxx:2074
#18 0x00007ffff6c28fac in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#19 0x00007ffff55bbeff in g_closure_invoke ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#20 0x00007ffff55ce56e in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#21 0x00007ffff55d67f9 in g_signal_emit_valist ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#22 0x00007ffff55d708f in g_signal_emit ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#23 0x00007ffff6d66c5c in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#24 0x00007ffff6d86cdb in gtk_window_propagate_key_event ()
from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#25 0x00007ffff6d8a15b in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#26 0x00007ffff6c28fac in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#27 0x00007ffff55bbfa5 in g_closure_invoke ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#28 0x00007ffff55ce56e in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#29 0x00007ffff55d67f9 in g_signal_emit_valist ()
---Type <return> to continue, or q <return> to quit---
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#30 0x00007ffff55d708f in g_signal_emit ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#31 0x00007ffff6d66c5c in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#32 0x00007ffff6c264c9 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#33 0x00007ffff6c281bc in gtk_main_do_event ()
from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#34 0x00007ffff6795ca2 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#35 0x00007ffff50e1197 in g_main_context_dispatch ()
from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#36 0x00007ffff50e13f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#37 0x00007ffff50e1712 in g_main_loop_run ()
from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#38 0x00007ffff6c27395 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#39 0x00007ffff79a0427 in main_lib (argc=1, argv=0x7fffffffd948) at libmain.c:1233
#40 0x00007ffff7365830 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6
#41 0x00000000004005d9 in _start ()
```
--
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/1385