#Geany documentation code#
#Geany documentation free#

#Geany documentation free#

It's not like there aren't any other free notepad applications out there.

#Geany documentation code#

In an earlier post you said 'LF' (carriage return), those are different characters, LF (newline) code 0x0A and CR (carriage return) code 0x0D, please confirm which you used.Įvery contributor to Geany is a volunteer, all of us give our own time to provide those contributions, so please be grateful for that. Please provide an exact set of steps to reproduce, please use the command line as only a few contributors are likely to have the file manager you are using, and may not have it configured the same as you, so we have no idea what command it is running and how it is running it. I don't understand the sequence of actions you took, if the file didn't open, why does Geany want you to save the file? Clearly something is missing. Your edit to the comment was missed, probably would have been better as another comment so it stood out, and github does not mail edits. Where s(he) has to kill the process in order to use the program again. So, it's not that we are stuck with using your application. It'll be a good starting point to keep friendly relations with the user base. Note that I've used up my precious resources to provide you with particulars including a screenshot when I could've simply ignored your response (and email). Otherwise, they may not bother getting back to you (especially with a case like mine where the solution or workaround became apparent to me soon afterwards).

You may need to provide the user with the reason(s) as to how come you are asking a user to do something. Just a note, contributors may not have a system capable of reproducing the problem immediately available, so you are asked to try things. The application could have a mechanism to catch the error/mistake by the user and offer options to solve it or better still handle it gracefully. If and when it happens accidentally, the application should not leave the user with a system where s(he) has to kill the process in order to use the program again. So such filenames should only ever happen accidentally, as in your case, and so be rare. The filename one sees on the screen and the actual filename are different, as you experienced until you realised the problem, so in some ways its better to not open such names, but Geany would not want to get into enforcing such limitations on filenames ↩įilenames should never have non-printing characters in them deliberately, this is a known spoofing mechanism1. Just concentrate on providing the requested information. So please do not try to attribute intentions to people trying to help you as in 'I presume this is just for troubleshooting purposes? Because you can't really ask the user to close Geany and open it through clicking on the offending file through the file manager every time s(he) wants to open that file'. It would require a re-engineering of the protocol to fix, and is only likely to happen if somebody provided a well written pull request with the changes. This is a line oriented protocol, as described here, so a line feed in the filename will terminate the filename early.įilenames should never have non-printing characters in them deliberately, this is a known spoofing mechanism 1. This confirms that the problem is in the protocol that transfers the filename to an existing instance so it opens in a tab. I've exited Geany completely, then clicked the test file with carriage return at the end of the file name. Please fix Geany so it opens the files with carriage returns (mistakenly added) when naming files or at least provide a more descriptive error. THen when I did tried to rename the file, thunar showed the carriage return on the file too. Renamed the directory by removing the carriage return.

The only way I stumbled across it was by copying the directory name then trying to paste it within thunar file manager (thinking it's something to do with dolphin) then thunar showed the carriage return. Odd that mousepad handles carriage returns on filenames but Geany doesn't or at least doesn't give a more descriptive error message. Must have copied the carriage return too. I tend to write the heading of the note (file) within geany, copy that, then save the file with the copied text as the filename. So, 'test file incorrect' 'LF' which was causing the unusual behaviour on Geany. It turned out I had a 'LF' (carriage return) at the end of the file name (possibly in the directory named 'test' too).