Re: [Github-comments] [geany/geany] Underscores missing with certain fonts, such as the default "Monospace Regular" font (#2386)

2021-02-10 Thread elextr
@bencaradocdavies so long as you put that in your user `filetypes.common` it will continue to override the default set in Geany so it doesn't matter what the default changes to. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHu

Re: [Github-comments] [geany/geany] Underscores missing with certain fonts, such as the default "Monospace Regular" font (#2386)

2021-02-10 Thread Ben Caradoc-Davies
As an aside, I also switched to (a slashed-zero variant of) Hack but stuck with ``` [styling] line_height=1;1; ``` in Geany because it gives me vertical spacing consistent with that in `xfce4-terminal` with the same font. -- You are receiving this because you are subscribed to this thread. Reply

Re: [Github-comments] [geany/geany] Underscores missing with certain fonts, such as the default "Monospace Regular" font (#2386)

2021-02-10 Thread elextr
@dregrad, We don't collect statistics about the number of Geany installs, but Github stats show about 10 clones _per day_ but that doesn't count the number of installs from distro repositories. So we can't compare the number of people who have problems with the number who use Geany. But the nu

Re: [Github-comments] [geany/geany-plugins] Markdown: Update using known GeanyDocument when available (#1064)

2021-02-10 Thread Colomban Wendling
@b4n commented on this pull request. > { - GeanyDocument *doc = document_get_current(); + if (!DOC_VALID(doc)) Wouldn't simply `doc == NULL` work here? Do you really get non-NULL doc pointers that have `doc->valid == FALSE`? -- You are receiving this because you are subscribed to this th

Re: [Github-comments] [geany/geany-plugins] Markdown: Update using known GeanyDocument when available (#1064)

2021-02-10 Thread Colomban Wendling
What your change suggests to me is that you'd encounter cases where `document_get_current()` doesn't return the document for which the signal was fired for. This sounds weird for the `activate`/`new`/`open`/`reload`/`filetype-set` signals you're using, and definitely something that should be f

Re: [Github-comments] [geany/geany-plugins] Markdown: Update using known GeanyDocument when available (#1064)

2021-02-10 Thread Colomban Wendling
@b4n commented on this pull request. > @@ -192,7 +193,7 @@ static gboolean on_editor_notify(GObject *obj, > GeanyEditor *editor, SCNotification *notif, MarkdownViewer *viewer) { if (IS_MOD_NOTIF(notif)) { -update_markdown_viewer(viewer); +update_markdown_viewer(viewer, NULL); ``

Re: [Github-comments] [geany/geany] Codes worked on other terminals but not on Geany (#2749)

2021-02-10 Thread Colomban Wendling
Normally support questions should rather go to the [mailing list](https://www.geany.org/support/mailing-lists/#geany-users) (or [IRC](https://www.geany.org/support/irc/)). In any case, we'll need more information than "Geany reported errors". What is your OS, Geany version, etc? A wild guess:

Re: [Github-comments] [geany/geany] Underscores missing with certain fonts, such as the default "Monospace Regular" font (#2386)

2021-02-10 Thread Damien Regad
Posting to a closed issue, as I don't want to open yet another issue for this. My setup: geany 1.36 (built on Mar 22 2020 with GTK 3.24.14, GLib 2.64.1) on Ubuntu 20.04.2 I can confirm the problem, not only with Default Monospace font (set to DejaVuSansMono.ttf), but also with quite a few other

[Github-comments] [geany/geany] Codes worked on other terminals but not on Geany (#2749)

2021-02-10 Thread zoehdn
I tried to run the following codes on Geany and it reported errors. The same codes worked fine on Google Colab. Can anyone help me here? Thanks. import re match=re.search(r'\d\s*\d\s*\d', 'xx1 2 3xx') match.group() -- You are receiving this because you are subscribed to this thread. Reply to

Re: [Github-comments] [geany/geany-plugins] Markdown Plugin (Feature Request): Keep scroll position on reload (#1055)

2021-02-10 Thread Matthew Brush
After a little more research I think it might be possible to do it fully within JS by loading the scroll position from the browser's localStorage (or maybe just sessionStorage) when the DOM is finished loading and saving it before the page is unloaded. If I can get that working, it should do the

Re: [Github-comments] [geany/geany-plugins] Markdown: Update using known GeanyDocument when available (#1064)

2021-02-10 Thread elextr
It can definitely return NULL for lots of reasons, but if it returns a pointer it should be valid since it tests it and returns NULL if not valid. -- 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

Re: [Github-comments] [geany/geany-plugins] Markdown: Update using known GeanyDocument when available (#1064)

2021-02-10 Thread Matthew Brush
I do not, I just noticed that it was giving invalid/NULL and that I had a valid document pointer already available. Probably one of the callbacks the plugin uses gets triggered early before the document list is fully initialized or something, but I didn't spend much time trying to understand it.