re: hotkeys in hotlist patch submitted

2003-02-03 Thread David Sterba
hi,

it works for me too :-)

i find the hotkeys very useful. in current implementation
i simulate hotkeys by placing the most visited dirs
to top and bottom (or near to), so this is about 4-6 dirs.

the Up button does not work (nothing happens).
i came across this just randomly, i cant remember i have used it,

i had one problem with compilation:
in hotlist.c:413 there is a declaration of variable inside
a block but after statments (C++ allowes this).

bye
dave
___
Mc-devel mailing list
[EMAIL PROTECTED]
http://mail.gnome.org/mailman/listinfo/mc-devel



hotlist: now with edit

2003-02-03 Thread bulia byak
An updated hotlist patch uploaded:

http://savannah.gnu.org/patch/index.php?func=detailpatchpatch_id=1042group_id=3521

Since nobody complained, I removed insert/append buttons; now it's 
one button saying add for new entry/group and done for 
edit entry/group. 

I also removed add current as redundant (new entry does the 
same with default values). 

Please report your experience. Please also share your ideas on 
these issues:

1. Hotkeys of entries may obscure the hotkeys of the buttons in 
the bottom of the list. Do we need to: block conflicting 
hotkeys from being entered, or warn the user, or disable button 
hotkeys?

2. Do we need to check for duplicate hotkeys in one group?

3. Does anyone know how to make a one-char-wide field for the 
hotkey?

4. Does anyone know how to display part of the line in a list
differently, e.g. to highlight the hotkey in each line of the
list?

-- 
__
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup

___
Mc-devel mailing list
[EMAIL PROTECTED]
http://mail.gnome.org/mailman/listinfo/mc-devel



RE: configure problem

2003-02-03 Thread [EMAIL PROTECTED]
Did anyone actually see this post?  This is still broken in CVS.  Am I the
only one who's had this problem?

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of [EMAIL PROTECTED]
Sent: Saturday, February 01, 2003 9:22 PM
To: [EMAIL PROTECTED]
Subject: RE: configure problem


Okay,
  This:

gettext_ver=`$GETTEXTIZE --version | \
  sed '2,$d;# remove all but the first line
   s/.* //; # take text after the last space
   s/-.*//; # strip -pre or -rc at the end
   s/\([^.]\+\)/0\1/g;  # prepend 0 to every token
   s/0\([^.][^.]\)/\1/g;# trim 0 from long lokens
   s/\.//g; # remove dots
   '`

  Seems to not work correctly on
  This:

www# gettextize --version
/usr/local/bin/gettextize (GNU gettext) 0.11.5
Copyright (C) 1995-1998, 2000-2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is
NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.
Written by Ulrich Drepper


I think what's happening here, is that the version of gettext is now 0.11.5,
and sed wacking this down to 0115 which the rest of the script seems to
interprit as being version 0.01.15, which is wrong.  Unfortunately, I'm not
a sed programmer, so I have no idea how to fix this in sed.  A perl hacker I
know thinks this would work:

gettextize --version|head -1|perl -ne 's/^.* ([0-9\.]+)$/$1/g; s/\.//g;
print;'

___
Mc-devel mailing list
[EMAIL PROTECTED]
http://mail.gnome.org/mailman/listinfo/mc-devel

___
Mc-devel mailing list
[EMAIL PROTECTED]
http://mail.gnome.org/mailman/listinfo/mc-devel



RE: configure problem

2003-02-03 Thread Pavel Roskin
Hello!

On Mon, 3 Feb 2003, [EMAIL PROTECTED] wrote:

 But after a subsequent cvs update -APCd, and it refreshed autogen.sh, it
 dies again as it did before.

It looks like a problem with the sed expression, and it's fixed in CVS.
You need revision 1.45.  Please note that the anonymous CVS is run on
several servers (currently 138.100.8.6 and 130.239.18.151), and
130.239.18.151 still has revision 1.44 as I'm writing this.  138.100.8.6
is up to date.

If you use anoncvs.gnome.org, you can see the files being replaced with
older revisions when anoncvs.gnome.org resolves to the server that doesn't
have the revision you have from another server.

The problem is not new.  I'll raise the issue with GNOME sysadmins.  If
they don't fix the problem, the mc CVS will move to savannah.gnu.org.

Please use this CVS root for now:

:pserver:[EMAIL PROTECTED]:2401/cvs/gnome

Use following commands to avoid the new checkout:

echo :pserver:[EMAIL PROTECTED]:2401/cvs/gnome newroot
find -name Root -exec cp newroot {} \;
rm newroot

 This is quite odd, not only did adding that tell me 0115, but then configure
 ran the rest of the way (almost) and ended with:
 ./configure: line 7953: syntax error near unexpected token `;'
 ./configure: line 7953: `;;'

That's much more serious than the problem with autogen.sh because
configure is distributed with the release.  However, my testing on FreeBSD
4.6.2 didn't exhibit this problem.  I was using a tarball, not CVS.

-- 
Regards,
Pavel Roskin
___
Mc-devel mailing list
[EMAIL PROTECTED]
http://mail.gnome.org/mailman/listinfo/mc-devel



RE: Much better now! (was RE: configure problem)

2003-02-03 Thread [EMAIL PROTECTED]
By the way, I get the same warnings on Slackware 8.1

configure.in:11: warning: do not use m4_patsubst: use patsubst or
m4_bpatsubst
configure.in:605: warning: do not use m4_regexp: use regexp or m4_bregexp

-Original Message-

Okay,
  I did a clean CVS pull from the source Pavel said to use.  ./autogen.sh
completes sucessfully now, with the following warnings, and no errors.

configure.in:11: warning: do not use m4_patsubst: use patsubst or
m4_bpatsubst
configure.in:605: warning: do not use m4_regexp: use regexp or m4_bregexp

___
Mc-devel mailing list
[EMAIL PROTECTED]
http://mail.gnome.org/mailman/listinfo/mc-devel