Re: Highlighting trailing spaces
On Wed, 05 Feb 2003, Pavel Roskin wrote: On Sun, 2 Feb 2003 03:34:10 +0100 Arpi [EMAIL PROTECTED] wrote: Btw, the Makefile syntax ruleset also contains an ugly part, showing TABs with bright red backround. It's even worse, as TABs are correct there. I like it - I don't forget to add TABs when adding new lines to Makefiles the Maybe it should be made less ugly? I tried but could not find any better color. What about black? I found it better then bright red. Vlad Romanenko. -- Ukrainian Postnuke translator http://uanuke.sourceforge.net/ ___ Mc-devel mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/mc-devel
[PATCH] Trivial fix for vfs/ChangeLog
Hello! This fixes spelling error in vfs/ChangeLog --- vfs/ChangeLog.orig 2002-12-30 12:09:43.0 +0200 +++ vfs/ChangeLog 2002-12-30 12:09:59.0 +0200 @@ -6,7 +6,7 @@ * extfs.c (read_archive): Free archive if the list command returned non-zero, return -1. - Initial implemntation from Adam Byrtek [EMAIL PROTECTED] + Initial implementation from Adam Byrtek [EMAIL PROTECTED] 2002-12-24 Pavel Roskin [EMAIL PROTECTED] ___ Mc-devel mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/mc-devel
Re: ALT ('-') and ALT('+')
Hello!
Is it reasonable to make ALT('=') do Select All as well? I use it all
the time and that triple bucky gets a bit... bothersome.
The code for the file selection keys is messy and needs a serious cleanup.
Adding new key combination to compensate for brokeness of the existing
code is hardly reasonable. Additional complexity will be an additional
obstacle for those who will clean up this code. People learn keys, and
then you can reassign those keys to something better.
There are several things you can do to make it more convenient for now.
You can use a terminal that has separate escape sequences for the keypad.
You can use only_leading_plus_minus. You can even use Learn keys to
assign your favorite combinations.
Have you tried Learn keys for that? If yes, why didn't you like this
approach? I think that the Learn keys dialog has two problems - one is
that users cannot find it when they need it. The other is that they don't
realize that it can help them.
The answer (hard, but still not ideal) would be to implement remappable
keys and a to write a much more complex dialog to assign keys to actions
(as opposed to matching physical keystrokes with escape sequences). This
would also mean stripping hardcoded keys from the menus, breaking all
translations. It was discussed many times, but nothing was done.
I think it can be said about the current state of the project that most of
the simple patches have been applied. The remaining stuff is mostly hard
and involves redesign. The unfortunate thing is that very few people
actually want to do the hard stuff. Most contibutors simply try to
overstretch old bad design. Remember e.g. chaining video players with
the || operator, which was an obvious (and wrong) extension of the same
idea for the Word doc viewers.
I see that those functions avoid the directories. It's a paltry matter
to comment out the lines in cmd.c that check for dirs, but there must be
a reason someone did that to begin with.
At least two reasons.
One is that the new dialogs are harder to code than to use input_dialog()
or other ready dialog. Just a little details - when XView was supported,
all the dialog had to be created backwards, i.e. starting with the widgets
that are last in the Tab order. Even the title of the dialog had to be
drawn manually until recently. Most importantly - the dialog API is
undocumented.
The other reason is that the selection for directories is in fact
supported. Just add slash at the end of the pattern. Usability of this
feature was obviously neglected, so that not only most users are unaware
of it, but even the developers trying to improve this code!
I cannot apply your patch for two reasons:
1) It makes it harder to select only files if I want to.
2) It replaces one random choice with another one instead of giving the
user the choice (and giving the choice to the user means a checkbox with
an obvious name, not an extra paragraph in the manual).
that way you can select all, then reverse the selection to get the
directories all selected? Two keystrokes.
Don't you realize that this inconsistency (invert affects directories,
select doesn't) is just another bug? It's not right, it's just tolerated
by users, unlike files on ftp beginning with 2000 :-)
Usually the subdirs are a minor component of a directory structure, and
it's the files you want to work on, usually.
Let the user decide. I'll appreciate if you check popular non-free file
managers (Far, Norton Commander, Windows Commander) and make the behaviour
consistent with at least with one of them if possible. At least some
users won't have to learn news keys when they start using mc.
Also, the unselect-all SHOULD do directories, shouldn't it. That's what
it's for, to unselect everything, isn't it? Right now it won't touch
selected directories. Isn't that wrong? If it's not wrong, could
someone please explain why?
Maybe because something (just like like you) didn't like writing new
dialogs?
--
Regards,
Pavel Roskin
___
Mc-devel mailing list
[EMAIL PROTECTED]
http://mail.gnome.org/mailman/listinfo/mc-devel
README typo fix.
Hi! Here is a small typo fix for the README file. Regards, Vlad. --- README Mon Sep 23 08:24:22 2002 +++ /home/vlad/my/projects/mc-orig/README Thu Sep 26 13:42:15 2002 @@ -38,7 +38,7 @@ Features -GNU Midnight Commander was conceived as a free close of John Socha's +GNU Midnight Commander was conceived as a free clone of John Socha's Norton Commander (TM). It also takes the best from more recent software with similar interfaces. GNU Midnight Commander comes with mouse support on xterm and optionally on the Linux console. ___ Mc-devel mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/mc-devel
Syntax file for M4/Autoconf - 2
Hello, Pavel! This looks very annoying. Too bright. Oh, I'm really sorry! I just forgot to switch to default color scheme. You know, the reason I started working on MC syntax files was I didn't' like its default colors. I prefer colors from pascal.syntax (I use console, not a terminal). So I modified c.syntax. I tried different colors to get the best color scheme for me and it wasn't easy since I had to replace multiply entries for same logical value (for example string, c-keyword, etc). So I turn syntax file to an M4 source, added macros like C_STRING_COLOR and put it everywhere. This way I separated color values from syntax rules. Then I put color values into separate file (I call it scheme) and include either colors.default.m4 or colors.bright.m4 when necessary. Now I have 13 syntax files being preprocessed and shared 2 color schemes for all syntax files. So changing colors is easy. :) You know, default colors for m4 now looks pretty, I even liked them although I usually prefer bright cvolors. New m4.syntax is attached. Put these lines in Syntax: file (..\*\\.m4$|configure.in) M4\sMacroprocessor\sSource include m4.syntax And add a line to syntax/Makefile.am Regards, Vlad Romanenko. m4.syntax Description: Binary data
Syntax file for M4/Autoconf
Hello! This time I'd like to contribute a syntax file for M4 macroprocessor with autoconf support. (m4.syntax attached) Put these lines in Syntax: file (..\*\\.m4$|configure.in) M4\sMacroprocessor\sSource include m4.syntax And add a line to syntax/Makefile.am Pavel, I'm sorry, but I misspelled word 'highlighting' in ChangeLog entry for js.syntax. I'd be glad if you corrected it (js.syntax-spelling.patch) Also, what do you think of adding numbers highlighting to C and Java syntax files? There are some more changes that I'd like to contribute to c.syntax such as - alphabetic sorting of keywords - better preprocessor directives highlighting - removing unnessesary syntax rules (for example we don't need to highlight '==' if there's '=') What do you think? Regards, Vlad Romanenko. js.syntax-spelling.patch Description: Binary data m4.syntax Description: Binary data
