Re: simple suggestions
Hello! > 1) To avoid appearing useless and disturbing messages in the command line > of "mc" (terminal version), I propose the simple modification of the > "mc.sh" attached here. If you are sending modifications, send a patch, not the whole file. This would ensure that the work of other people modifying the same file won't be lost. Only if the changes are so radical that the patch would be longer than the file itself, send the whole file, but make sure to mention the base version, so that if there have been any changes after that version, they could be reviewed and applied to your version. In this particular case, version 4.6.0 requires an argument after "-P", so your patch will actually cause "useless and disturbing messages". I believe that the approach taken in mc-4.6.0 (alias to a script) is more reliable than the approach you are trying to fix (shell function). > 2) To make work with "mc" in "xterm" more comfortable (proper work of > "Alt" and "Esc" keys), I propose the X-defaults for the "xterm" attached > in the file "Xdefaults.mc" here. Sometimes Escape-something is more convenient than Alt-something. For example, I prefer Escape Shift-/ to Alt-Shift-/ to activate "Find File". Besides, it's better to have consistent behavior on different terminals, including other people's machines. But it's a question of taste. > For Russian users I could recommend the X-defaults listed in > "Xdefaults.mc.rus" that send proper "Alt"-codes in the Russian mode. It's a nice idea. I often miss Atl-P in the editor when I'm in the Cyrillic mode. On the other hand, you'll lose the hotkeys in Russian locale. That's another case when you need single Escape. Maybe it's better to fix the XFree86 keyboard definition so that it would "forget" the charset state when Alt is pressed, just like it's done with Ctrl. Anyway, there was a discussion about creating a "contrib" directory that would include such things. I think I'll create it on the website when I have time. Xdefaults.mc.rus would go there. -- Regards, Pavel Roskin ___ Mc-devel mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/mc-devel
simple suggestions
Dear Sir,
1) To avoid appearing useless and disturbing messages in the command line
of "mc" (terminal version), I propose the simple modification of the
"mc.sh" attached here.
2) To make work with "mc" in "xterm" more comfortable (proper work of
"Alt" and "Esc" keys), I propose the X-defaults for the "xterm" attached
in the file "Xdefaults.mc" here. For Russian users I could recommend the
X-defaults listed in "Xdefaults.mc.rus" that send proper "Alt"-codes in
the Russian mode.
Best regards,
Michael Lashkevich
mc.sh
Description: mc.sh
xterm*deleteIsDEL: true
xterm*eightBitInput: false
xterm*VT100.Translations: #override\n\
Escape : string(0x1b) string(0x1b)
xterm*deleteIsDEL: true
xterm*eightBitInput: false
xterm*VT100.Translations: #override\n\
Escape : string(0x1b) string(0x1b)\n\
Meta ~ShiftCyrillic_shorti: string(0x1b) string("q")\n\
Meta ShiftCyrillic_shorti: string(0x1b) string("Q")\n\
Meta ~ShiftCyrillic_tse: string(0x1b) string("w")\n\
Meta ShiftCyrillic_tse: string(0x1b) string("W")\n\
Meta ~ShiftCyrillic_u: string(0x1b) string("e")\n\
Meta ShiftCyrillic_u: string(0x1b) string("E")\n\
Meta ~ShiftCyrillic_ka: string(0x1b) string("r")\n\
Meta ShiftCyrillic_ka: string(0x1b) string("R")\n\
Meta ~ShiftCyrillic_ie: string(0x1b) string("t")\n\
Meta ShiftCyrillic_ie: string(0x1b) string("T")\n\
Meta ~ShiftCyrillic_en: string(0x1b) string("y")\n\
Meta ShiftCyrillic_en: string(0x1b) string("Y")\n\
Meta ~ShiftCyrillic_ghe: string(0x1b) string("u")\n\
Meta ShiftCyrillic_ghe: string(0x1b) string("U")\n\
Meta ~ShiftCyrillic_sha: string(0x1b) string("i")\n\
Meta ShiftCyrillic_sha: string(0x1b) string("I")\n\
Meta ~ShiftCyrillic_shcha: string(0x1b) string("o")\n\
Meta ShiftCyrillic_shcha: string(0x1b) string("O")\n\
Meta ~ShiftCyrillic_ze: string(0x1b) string("p")\n\
Meta ShiftCyrillic_ze: string(0x1b) string("P")\n\
Meta ~ShiftCyrillic_ha: string(0x1b) string("[")\n\
Meta ShiftCyrillic_ha: string(0x1b) string("{")\n\
Meta ~ShiftCyrillic_hardsign: string(0x1b) string("]")\n\
Meta ShiftCyrillic_hardsign: string(0x1b) string("}")\n\
Meta ~ShiftCyrillic_ef: string(0x1b) string("a")\n\
Meta ShiftCyrillic_ef: string(0x1b) string("A")\n\
Meta ~ShiftCyrillic_yeru: string(0x1b) string("s")\n\
Meta ShiftCyrillic_yeru: string(0x1b) string("S")\n\
Meta ~ShiftCyrillic_ve: string(0x1b) string("d")\n\
Meta ShiftCyrillic_ve: string(0x1b) string("D")\n\
Meta ~ShiftCyrillic_a: string(0x1b) string("f")\n\
Meta ShiftCyrillic_a: string(0x1b) string("F")\n\
Meta ~ShiftCyrillic_pe: string(0x1b) string("g")\n\
Meta ShiftCyrillic_pe: string(0x1b) string("G")\n\
Meta ~ShiftCyrillic_er: string(0x1b) string("h")\n\
Meta ShiftCyrillic_er: string(0x1b) string("H")\n\
Meta ~ShiftCyrillic_o: string(0x1b) string("j")\n\
Meta ShiftCyrillic_o: string(0x1b) string("J")\n\
Meta ~ShiftCyrillic_el: string(0x1b) string("k")\n\
Meta ShiftCyrillic_el: string(0x1b) string("K")\n\
Meta ~ShiftCyrillic_de: string(0x1b) string("l")\n\
Meta ShiftCyrillic_de: string(0x1b) string("L")\n\
Meta ~ShiftCyrillic_zhe: string(0x1b) string(";")\n\
Meta ShiftCyrillic_zhe: string(0x1b) string(":")\n\
Meta ~ShiftCyrillic_e: string(0x1b) string(0x27)\n\
Meta ShiftCyrillic_e: string(0x1b) string(0x22)\n\
Meta ~ShiftCyrillic_ya: string(0x1b) string("z")\n\
Meta ShiftCyrillic_ya: string(0x1b) string("Z")\n\
Meta ~ShiftCyrillic_che: string(0x1b) string("x")\n\
Meta ShiftCyrillic_che: string(0x1b) string("X")\n\
Meta ~ShiftCyrillic_es: string(0x1b) string("c")\n\
Meta ShiftCyrillic_es: string(0x1b) string("C")\n\
Meta ~ShiftCyrillic_em: string(0x1b) string("v")\n\
Meta ShiftCyrillic_em: string(0x1b) string("V")\n\
Meta ~ShiftCyrillic_i: string(0x1b) string("b")\n\
Meta ShiftCyrillic_i: string(0x1b) string("B")\n\
Meta ~ShiftCyrillic_te: string(0x1b) string("n")\n\
Meta ShiftCyrillic_te: string(0x1b) string("N")\n\
Meta ~ShiftCyrillic_softsign: string(0x1b) string("m")\n\
Meta ShiftCyrillic_softsign: string(0x1b) string("M")\n\
Meta ~ShiftCyrillic_be: string(0x1b) string(",")\n\
Meta ShiftCyrillic_be: string(0x1b) string("<")\n\
Meta ~ShiftCyrillic_yu: string(0x1b) string(".")\n\
Meta ShiftCyrillic_yu: string(0x1b) string(">")\n\
Meta ~ShiftCyrillic_io: string(0x1b) string("/")\n\
Meta ShiftCyrillic_io: string(0x1b) string("?")
Re: File find: open viewer does not jump to line?
On Fri, 7 Feb 2003 20:16:36 +0100 David Sterba <[EMAIL PROTECTED]> wrote: > Hi, > > > Give more details. Describe: > > > > 1) What you do. > I open the file find dialog. Enter the string to search. Press OK to start > search. Wait until some files are found. Go to the entry, pres F3. The > internal viewer opens. Press F5 (view current line). It always show 1, > although the found entry says e.g. "ChangeLog:1054". > > > 2) What you expect to get. > I expect to be positioned to line 1054. > > > 3) What you actually get. > The file position is always on first line. > > > If you are using external viewer and editor, starting on a certain line is > > not supported for an obvious reason - different viewers and editors may > > have different command line switches for that. Actually, all editors which I have installed (vim, nvi, jed, joe, nano, pico, nedit, emacs) accept using "$EDITOR +number file" to jump to line number. I have made a patch (and posted it to mc-devel some time ago) to support adding "+number" option for external editors. Do you know unix text editors which doesn't support this option? Are there any more reasons to not apply it (of course, not counting that it is a bit ugly, it has to add passing an argument to called program). -- Filip Kalinski <[EMAIL PROTECTED]> ___ Mc-devel mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/mc-devel
Re: File find: open viewer does not jump to line?
Hi, > You can try this before running mc: > > $ cd > $ mv .mc .mc-old > (and may be) > > Sometimes fresh configuration solves strange problems. Yes, it works now. Dave ___ Mc-devel mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/mc-devel
Re: File find: open viewer does not jump to line?
On Fri, 7 Feb 2003, David Sterba wrote: > > 1) What you do. > I open the file find dialog. Enter the string to search. Press OK to start > search. Wait until some files are found. Go to the entry, pres F3. The > internal viewer opens. Press F5 (view current line). It always show 1, > although the found entry says e.g. "ChangeLog:1054". > > > 2) What you expect to get. > I expect to be positioned to line 1054. > > > 3) What you actually get. > The file position is always on first line. > > > If you are using external viewer and editor, starting on a certain line is > > not supported for an obvious reason - different viewers and editors may > > have different command line switches for that. By the way, 'man mcview' does not contain the description of the "goto line" switch. What is it? > This happens with the internal viewer. You can try this before running mc: $ cd $ mv .mc .mc-old (and may be) Sometimes fresh configuration solves strange problems. ...Bye..Dmitry. ___ Mc-devel mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/mc-devel
Re: File find: open viewer does not jump to line?
Hi, > Give more details. Describe: > > 1) What you do. I open the file find dialog. Enter the string to search. Press OK to start search. Wait until some files are found. Go to the entry, pres F3. The internal viewer opens. Press F5 (view current line). It always show 1, although the found entry says e.g. "ChangeLog:1054". > 2) What you expect to get. I expect to be positioned to line 1054. > 3) What you actually get. The file position is always on first line. > If you are using external viewer and editor, starting on a certain line is > not supported for an obvious reason - different viewers and editors may > have different command line switches for that. This happens with the internal viewer. bye David ___ Mc-devel mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/mc-devel
Re: File find: open viewer does not jump to line?
Hello! > [in mc 4.6.0] > opening editor/viewer in file find dialog does not go to the line. > I think, it worked in the past versions. Give more details. Describe: 1) What you do. 2) What you expect to get. 3) What you actually get. Opening files in the internal viewer and editor works for me in the way I expect it to work. If you are using external viewer and editor, starting on a certain line is not supported for an obvious reason - different viewers and editors may have different command line switches for that. -- Regards, Pavel Roskin ___ Mc-devel mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/mc-devel
Re: File find: open viewer does not jump to line?
Hi, > Hello David. > > On Fri, 7 Feb 2003, David Sterba wrote: > > [in mc 4.6.0] > > opening editor/viewer in file find dialog does not go to the line. > > I think, it worked in the past versions. > > Strange. > It works for me. I just compiled and tried the latest CVS version, but it still does not work. Maybe the error is only at me. Well, I'll try to find out what's wrong. bye Dave ___ Mc-devel mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/mc-devel
Re: File find: open viewer does not jump to line?
Hello David. On Fri, 7 Feb 2003, David Sterba wrote: > [in mc 4.6.0] > opening editor/viewer in file find dialog does not go to the line. > I think, it worked in the past versions. Strange. It works for me. ...Bye..Dmitry. ___ Mc-devel mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/mc-devel
File find: open viewer does not jump to line?
Hi, [in mc 4.6.0] opening editor/viewer in file find dialog does not go to the line. I think, it worked in the past versions. bye Dave ___ Mc-devel mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/mc-devel
