The "Start in:" field in the Geanly.lnk should be empty, it's currently set to
the install dir and this prevents command-line invocations from opening
relative-pathed file arguments correctly.
Also it would be useful for scripting/debug to have a mode where geany stays
attached to the launch cm
Invoking `C:\Program Files (x86)\Geany\Geany foo.txt` for some existing file
`foo.txt` in your current dir (or at any relative path) fails because the link
has a "Start in:" value set; leaving this empty makes it work as expected.
--
You are receiving this because you are subscribed to this thr
Markdown freezes geany for about 10s on my Win10 system when starting up. I've
verified that disabling/enabling markdown is what's causing the delay.
--
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/g
After startup too, but only the first time (and apparently only for 1.29, 1.28
seems to be fine)
--
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/519#issuecomment-275002643
I've tried to repro a bunch of times on 1.28, haven't hit it. It happens 100%
of the time on 1.29 (with the caveat that that's on a different machine). I'll
try upgrading the 1.28 machine. FWIW I only started noticing this when I
upgraded my work machine to 1.29.
--
You are receiving this beca
My very brief experiment was that loading/unloading was fast after the first
time. Restarting Geany went back to slow.
--
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/519#issueco
I just upgraded from 1.28 -> 1.31 and Geany has started popping a "No Disk"
dialog on startup (Cancel/Continue 3 times gets past this):
I grepped through the config files under %appdata%
I've got a win10 machine with 3 monitors, the primary is a 4k laptop display
scaled by 200%. The mouse pointer is unscaled in the text edit window when
geany is on the 200%-scaled desktop, making it very hard to see.
--
You are receiving this because you are subscribed to this thread.
Reply to
Looks like support landed in 3.x?
https://bugzilla.gnome.org/show_bug.cgi?id=768081
Are the pointers in the text edit area custom? Could geany be patched to just
use the system default pointers when hiDPI is detected?
--
You are receiving this because you are subscribed to this thread.
Reply to
Yup.
--
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/1571#issuecomment-321946817
10 matches
Mail list logo
