Geany version: 1.33
If the compilation of file A modifies file B, the scrollbar in file B doesn't move after the compilation.
How to reproduce:
1. Start compilation of some file. It has to modify another opened file.
2. Switch to the other file that has been modified by the compilation.
3. In appearing message window, "The file _\<filename\>_ on the disk is more recent than the current buffer.", reload the file.
4. Finished. Now the scrollbar of the modified file won't move
[Here is a video of the bug reproduction (zipped)](https://github.com/geany/geany/files/2169464/geany-bug-demonstrati…).
--
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/1893
@thwaller Geany print to PDF will print the markdown source, it will not convert the markup to PDF (which it sounds like you expect). You can define a build command to convert to run your markdown converter to pdf and print.
Colour printing of the source is intended to replicate the way the source is styled in the editor pane, but it was not designed to handle the current prevalence of dark themes.
--
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/617#issuecomment-985118195
Are there any updates on this? I have never needed or used the printing functionality before. I started trying it now as Typora, the markdown software I was using, changed to paid software. So I thought to give Geany a shot as being the new editor. For me, I do a lot of export to pdf, which Geany does not provide as an option, even in extensions from what I can see. I can however print to file -> PDF. I am using `Kugel` appearance and my print output is as described here... a white page with text I cannot read, it is almost white.
Just sharing my opinion, I see little need for color printing in Geany. Maybe I am wrong and others do. That said, I concur with the idea of making the default print output as monochrome, maybe even with the ability to change the opacity of the printing, like 50% to 100% or something.
I wanted to add my scenario so current circumstance that this is needed, is an issue, can be seen. While Geany is not really a "markdown editor", I think it now has more use to me. Any time I can reuse existing software, that is a good thing :)
--
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/617#issuecomment-985111171
This pull request removes the geany_ prefix from parsers we can sync easily with ctags and which contain only small changes and copies over these parsers from uctags (the versions from tag p5.9.20211031.0 like in #2984). More details can be found in the commit messages.
I plan to do the same with other parsers too, this pull request just includes those that didn't contain many changes to make this pull request easy to review. This pull request compiles fine independently of whether #2984 is applied or not.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2990
-- Commit Summary --
* <a href="https://github.com/geany/geany/pull/2990/commits/1756f0cbc27338f63eda500a4a…">Remove the geany_ prefix from parsers with trivial changes against ctags</a>
* <a href="https://github.com/geany/geany/pull/2990/commits/7dbbd1bee2ea1c2dca7343c471…">Update parsers to the uctags versions and update Geany where needed</a>
-- File Changes --
M ctags/Makefile.am (30)
R ctags/parsers/abaqus.c (12)
R ctags/parsers/abc.c (65)
R ctags/parsers/asciidoc.c (6)
R ctags/parsers/bibtex.c (22)
R ctags/parsers/cobol.c (0)
R ctags/parsers/css.c (1)
R ctags/parsers/erlang.c (3)
R ctags/parsers/flex.c (16)
R ctags/parsers/haskell.c (16)
R ctags/parsers/haxe.c (10)
R ctags/parsers/json.c (54)
R ctags/parsers/julia.c (0)
R ctags/parsers/powershell.c (17)
R ctags/parsers/rst.c (59)
R ctags/parsers/txt2tags.c (10)
M src/tagmanager/tm_parser.c (22)
M tests/ctags/rules.t2t.tags (6)
M tests/ctags/titles.t2t.tags (24)
-- Patch Links --
https://github.com/geany/geany/pull/2990.patchhttps://github.com/geany/geany/pull/2990.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/2990
I suspect this might be a problem with the editor module, but I think the issue should be raised here.
I'm using geany:
on Slackware64-current Linux,
geany 1.38 (built on 2021-11-23 with GTK 3.24.29, GLib 2.68.2)
I configged the editor fron as 'Bitstream Vera Sans Mono Roman' at 11 points.
At this scale, underscores are not renderered.
When I scale the font up or down, using ctrl-- or ctl-+, the underscore reappears.
Of course I could probably change the font, but I have had some problems with
other mono-spaced fonts which have unicode-characters defined correctly (apart
from taste issues)
I have the impression that this might have appeared on upgrading to 1.38. I can't
remember if I ever noticed this before.
John
--
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/3038
The filename from commandline argument is being processed directly, without first resolving symlinks. This leads to bug #1567, where Geany fails to open existing file, if it is being opened using path containing symlink and relative directories.
Windows counterpart of this code actually resolves the links, I have just corrected the non-win branch. This fixes the bug described in the bug report and should not have any unwanted side-effects.
Similar problem might (or might not) be also present in two other functions that use utils_tidy_path, without resolving the symlinks first:
- in `document_new_file` at [src/document.c:832](https://github.com/geany/geany/blob/b524a58e12e85c94a32…
- in `get_custom_plugin_path` at [src/plugins.c:1009](https://github.com/geany/geany/blob/b524a58e12e85c94a32…
I'm not sure if it is appropriate to check and possibly fix those in the same PR.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3036
-- Commit Summary --
* resolve symlink before the path is tidied (#1567)
-- File Changes --
M src/document.c (2)
-- Patch Links --
https://github.com/geany/geany/pull/3036.patchhttps://github.com/geany/geany/pull/3036.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/3036