I believe formerly in 121 or around there, editing of files was allowed Im not sure what happened, but this seems to be the case no longer Pluma, does this operation just fine, as does libre office, and some other file editors When I try to explicitly run geany to open a file across the network, geany will open but the file will not The types of connections
Here it is working in pluma, which is what I would like to see fixed in geany Pluma is a fine text editor, but I like Geany far more
are for me, ssh, and sftp
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/893
This implements working directories in the geanyprj plugin.
The motivation is to be able to 'make' via build menu shortcut within Geany when the project is set up with CMake and uses some far away build directory.
It syncs with Geany's own build menu working directories, while giving precedence to the main project system.
Comments/improvements welcome.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/486
-- Commit Summary --
* added working directory (non-ft building) support in geanyprj
* geanyprj working directory input field in preference dialog
* geanyprj working directories now sync with Geany's build dialog
-- File Changes --
M geanyprj/src/geanyprj.c (2)
M geanyprj/src/geanyprj.h (3)
M geanyprj/src/menu.c (18)
M geanyprj/src/project.c (16)
M geanyprj/src/utils.c (10)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/486.patchhttps://github.com/geany/geany-plugins/pull/486.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-plugins/pull/486
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