On Sun, 29 Mar 2015 09:52:46 +0200 Frank Dietrich wrote:
I have a quick question: Is it enough to report an issue on
https://github.com/MidnightCommander/mc/issues
We (developers) don't use github as issue tracker.
or should it be reported anywhere else also?
Please report any issue here:
MC has three config options for what to do after executing files by
pressing return with the selection on them:
1 Close the shell every time, returning to MC
2 Leave the window open every time, press return to... return
3 Close the window only on dumb terminals (what?)
Number one leaves you
I see many `if (strcmp (a, b) == 0)` in the code. Wouldn't it be nice
if we create a macro and then do `if (STREQ (a,b))` instead?
(Not that it bothers me much. I ask this mainly to verify that my
subscription works and that I can post here ;-)
___
I agree. What I did was check Never on Pause after run
and put reads in the menu/ext files where I knew I would
want the pause. Something like this:
+ t r ! t t
@ Do something on the current file
CMD=%{Enter command}
$CMD ./%0f
read -e -n1
I agree. What I did was check Never on Pause after run
and put reads in the menu/ext file
Oho, that's *very* clever, thank you!
On Sun, Mar 29, 2015 at 10:14 AM, Mike Smithson mdooli...@gmail.com wrote:
I agree. What I did was check Never on Pause after run
and put reads in the menu/ext
On Sun, 2015-03-29 at 18:18 +0300, Mooffie wrote:
I see many `if (strcmp (a, b) == 0)` in the code. Wouldn't it be nice
if we create a macro and then do `if (STREQ (a,b))` instead?
Nope, because there is no point in that beyond obfuscating the code.
(Not that it bothers me much. I ask this
