Just for the benefit of anybody reading this, to be clear, Geany only cannot to open a file if it cannot recognise the __encoding__, it does not have to recognise a filetype or language.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/3687#discussioncomment-7570341
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/repo-discussions/3687/comments/7570341(a)github.com>
`Menu->Search->Find in Files` ?
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/3687#discussioncomment-7570297
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/repo-discussions/3687/comments/7570297(a)github.com>
Closed #3687 as resolved.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/3687
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/repo-discussions/3687/discussion_event/954367(a)github.com>
I'm not specifically talking about editing a source file that contains a NUL character. I'm talking about not being able to quickly peek at just any file and this is where Geany is limited (read only would have been enough for me). Geany refuses to open files that it does not recognize and this is what I call limiting. NotePad++ under Windows opened ANYTHING and never complained about not being able to recognize the file format or the language. It would display anything as plain text, even binary files.
I'm well aware of other utilities for this kind of job such as hex editors (which I also have) but I like to be able to quickly peek at files without switching apps when I'm working in an IDE. Kate under macOS looks to be a closer replacement to NotePad++ as it not only lets you open any (binary or whatever) file you want, but it also has a "Find in files" function, which I could not find in Geany unfortunately.
Thanks again for trying to help and good luck with Geany.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/3687#discussioncomment-7565252
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/repo-discussions/3687/comments/7565252(a)github.com>
Rewriting as C++ would only help a little, so it proabaly could read NULs, but it is still required to be (convertible to) UTF-8.
Just a query, why is it so limiting? What languages have embedded NULs?
Geany is a lightweight IDE which edits text files, and can build applications from them, thats its use-case, and then Unicode covers all text. Its use-case does not include examining and patching binary files.
If you have a use-case for reading/modifying binary it would be better to use the right tool, one that is designed to handle unformatted binary.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/3687#discussioncomment-7562487
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/repo-discussions/3687/comments/7562487(a)github.com>
Is there a way for Geany to stop producing a dot underscore file such as ._example.php whenever I save example.php ? I'm working on a Windows volume and I understand macOS will make some system files on foreign drive formats, but I would like to know if at least Geany could edit the file and not create a side file for every file I edit with it?
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3685
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3685(a)github.com>
Is there a way to force Geany to open ANY file it doesn't recognize as plain text or ASCII? I don't care for syntax on some of the files, I just want to see the raw contents. NotePad++ didn't have any issue in opening whatever and displaying it (even binary files) so can Geany do that?
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3686
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3686(a)github.com>
Geany 2.0 comes with a few broken colour scheme templates. Look at the brace_good line in the following screenshot, you will see a typo where there's a comma instead of a semicolon:
<img width="1488" alt="282243403-bd321a08-adc3-461b-807a-145057b4bb9e" src="https://github.com/geany/geany-themes/assets/13210399/9ee385b4-8a8a-4e6f-b5…">
When I fix that line, it works properly and braces are highlighted, otherwise (by default) they're black on dark gray, so the highlighting is almost completely unnoticeable.
Please fix your schemes, the line should be reading:
brace_good=pro_orange;pro_selection_background;true;false
Make sure to also check the light scheme from the same name as it contains the same typo! ;-)
Issue initially raised over at Geany 2.0 GitHub: https://github.com/geany/geany-osx/issues/50#issuecomment-1806816745
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-themes/issues/65
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-themes/issues/65(a)github.com>
Geany 1.38, 2.0
In the editor right click menu, the editing functions (move line, comment line etc) act on the line with the caret on it, not the line clicked on. But the inserts (date, comment etc) act where the click happens.
This inconsistency is a footgun waiting to shoot, thankfully undo is available.
I can see why it happens, the things that are caret related are copies of normal menu items, which have no click position, only the caret. Maybe its as simple as right click moving the caret to the click position before calling the normal menu item.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3683
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3683(a)github.com>