@elextr thanks for responding. I should comment on something you said, which I think gets to the heart of the matter:

If you feel you have a use-case, remember, that suggests it is your use-case, not anybody elses. On that basis you would be more likely to succeed if you presented a small, simple, well written and documented pull-request rather than trying to persuade others it is their problem.

(Or use the workarounds like -c or different sudo configuration)

Answers to your two questions:

1. Although I'm a developer and contribute to the open-source community on other fronts, I don't write in C; but more importantly, have no time or bandwidth as a guy just wanting to get other stuff done, in issuing a pull request on every project that has a bug. If I can't use my skills of logic to "persuade others it is their problem", then I guess it will have to go unfixed, and I use any one of a couple dozen other lightweight GUI editors.
2. As a regular desktop user who just wants to get stuff done and not muck around with command-line options (unless I'm actually developing something myself), I have already implemented a workaround: I use another editor now. I've updated my three scripts that I use for almost everything text-related, to just invoke a different editor. Problem solved. None of the other common editors out there has this problem. Not gedit, leafpad, mousepad, brackets, etc. (Nor vi or nano either, for that matter.)

No one working on geany getting paid, presumably, but there is a reason you do this, right? I don't know what those reasons are, but I know I for one like to have more and more satisfied users. At least, that drives me and studies show drives many other open-source developers.

You guys made one of the best lightweight editors around. It just seems such a shame to lose users for no good reason - and in fact for a pointlessly, rigidly dogmatic reason. You can blame it all day long on the sudo program, but the bottom line is there are close to a dozen similar editors - just that I know of first-hand - that don't exhibit this behavior. (In fact no other editor I've tried, period.)

Working around underlying bugs in the stack that we have no control over is an inevitable part of developing software. I'd wager half of any code base that consumes underlying services is doing just that. Refusing to do so doesn't make it any less of your bug, because it still affects your users.

It doesn't affect "just" me. If you google this problem you'll get back pages of very specific results pointing to countless user forums.

Like I said, you guys are volunteers (presumably) doing fantastic work. I can't be "upset" at some of these responses that don't "get it". (Get it? Gedit?). And by "get it", I mean from the perspective of their users who don't care that it's a bug in one of the most commonly used programs in all of *nix, or care about c domain sockets, nor worry about how a temp file shouldn't exist in a user profile directory. All that means is that some of your users can't sudo geany and will have to find a different editor, and most of the time you'll never hear about it.

Trust me, I understand that breaking time-honored conventions can cause more problems for everyone now and down the road. I'm not suggesting the solution is that you store a temp file in a user configuration directory. But isn't this seemingly "intractable problem" why c library functions like mktemp exist?

Thanks guys. While I'm set for now with a different editor, I'm sad to see geany go from my workflow, and will check back once every several months or so to see if I can, as a test case:

geany &> /dev/null & disown; sudo geany

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.