Re: [PATCH] RPM vfs ignores conflicts

2006-11-01 Thread Jindrich Novy
Hi Leonard, On Tue, 2006-10-31 at 20:44 +0100, Leonard den Ottolander wrote: Hi Jindrich, On Tue, 2006-10-31 at 16:07 +0100, Jindrich Novy wrote: the current RPM vfs allows to see RPM package requires/provides and obsoletes but lacks an implementation of conflicts. The attached patch

Re: [PATCH] RPM vfs ignores conflicts

2006-11-01 Thread Leonard den Ottolander
Hi Jindrich, On Wed, 2006-11-01 at 10:23 +0100, Jindrich Novy wrote: sure :) here we go with the patched trpm vfs as well. rpms fortunately doesn't need any changes. Yes, of course, trpm. Committed. Thanks. Leonard. -- mount -t life -o ro /dev/dna /genetic/research

Re: [bug #18042] cannot specify port number in shell link

2006-11-01 Thread Leonard den Ottolander
Hello Andrew, On Mon, 2006-10-30 at 12:04 +, Andrew V. Samoilov wrote: Follow-up Comment #3, bug #18042 (project mc): Do I understand correctly that a port number *can* be combined with C _or_ r? No. Look at utilvfs.c:vfs_split_url(). No one syntax change. Only undocumented behaviour

Re: [bug #18042] cannot specify port number in shell link

2006-11-01 Thread Pavel Tsekov
On Wed, 1 Nov 2006, Leonard den Ottolander wrote: Hello Andrew, On Mon, 2006-10-30 at 12:04 +, Andrew V. Samoilov wrote: Follow-up Comment #3, bug #18042 (project mc): Do I understand correctly that a port number *can* be combined with C _or_ r? No. Look at utilvfs.c:vfs_split_url().

Re: [bug #18136] MC wont work with new bash-3.2 propeply with all directories.

2006-11-01 Thread Pavel Tsekov
On Tue, 31 Oct 2006, Leonard den Ottolander wrote: On Mon, 2006-10-30 at 11:45 +0200, Pavel Tsekov wrote: IMO, if you intend to work on a fix you should follow the suggestion of the bash maintainer to switch over to using printf - not only for bash but for all cases. Of course a fallback

Re: [bug #18136] MC wont work with new bash-3.2 propeply with all directories.

2006-11-01 Thread Pavel Tsekov
On Wed, 1 Nov 2006, Thomas Dickey wrote: On Wed, 1 Nov 2006, Pavel Tsekov wrote: Yes, I read that comment. However I'm not prepared to start breaking the functionality of shells that I never use. This is a rather strange statement. As a developer you should try to go beyond your personal

Re: [bug #18136] MC wont work with new bash-3.2 propeply with all directories.

2006-11-01 Thread Thomas Dickey
On Wed, 1 Nov 2006, Pavel Tsekov wrote: On Wed, 1 Nov 2006, Thomas Dickey wrote: On Wed, 1 Nov 2006, Pavel Tsekov wrote: Yes, I read that comment. However I'm not prepared to start breaking the functionality of shells that I never use. This is a rather strange statement. As a developer

Re: [bug #18136] MC wont work with new bash-3.2 propeply with all directories.

2006-11-01 Thread Pavel Tsekov
On Wed, 1 Nov 2006, Thomas Dickey wrote: On Wed, 1 Nov 2006, Pavel Tsekov wrote: On Wed, 1 Nov 2006, Thomas Dickey wrote: On Wed, 1 Nov 2006, Pavel Tsekov wrote: Yes, I read that comment. However I'm not prepared to start breaking the functionality of shells that I never use. This is

Re: [bug #18136] MC wont work with new bash-3.2 propeply with all directories.

2006-11-01 Thread Thomas Dickey
On Wed, 1 Nov 2006, Pavel Tsekov wrote: Ok. Since I am not native english speaker I cannot judge whether he is recommending it or not. In any case I can see why keeping the old behaviour of 'echo' is important for large scripts, however what we have in MC is nothing as big. I just feel that

Re: [bug #18136] MC wont work with new bash-3.2 propeply with all directories.

2006-11-01 Thread Leonard den Ottolander
Hello Pavel, On Wed, 2006-11-01 at 13:27 +0200, Pavel Tsekov wrote: Yes, I read that comment. However I'm not prepared to start breaking the functionality of shells that I never use. This is a rather strange statement. As a developer you should try to go beyond your personal preferences.

Re: [bug #18136] MC wont work with new bash-3.2 propeply with all directories.

2006-11-01 Thread Pavel Tsekov
On Wed, 1 Nov 2006, Thomas Dickey wrote: On Wed, 1 Nov 2006, Pavel Tsekov wrote: Ok. Since I am not native english speaker I cannot judge whether he is recommending it or not. In any case I can see why keeping the old behaviour of 'echo' is important for large scripts, however what we have

Re: [bug #18136] MC wont work with new bash-3.2 propeply with all directories.

2006-11-01 Thread Leonard den Ottolander
On Wed, 2006-11-01 at 14:55 +0200, Pavel Tsekov wrote: I am beginning to wonther whether do we really want to escape the characters using echo or printf. For embedded backslashes etc. I suppose we do. Leonard. -- mount -t life -o ro /dev/dna /genetic/research

Re: [bug #18136] MC wont work with new bash-3.2 propeply with all directories.

2006-11-01 Thread Leonard den Ottolander
Hello Thomas, On Wed, 2006-11-01 at 07:51 -0500, Thomas Dickey wrote: Before rushing off to change things to accommodate bash 3.2, it's worth checking if the fix will work with other shells. I'm not quite sure which fix you are referring to here. The temporary hack I send to this list

Re: [bug #18042] cannot specify port number in shell link

2006-11-01 Thread Leonard den Ottolander
Hello Pavel, On Wed, 2006-11-01 at 13:20 +0200, Pavel Tsekov wrote: IMO, it would be better if MC pops up an url specific dialog for each vfs if necessary so that the user could finer tune the connection. I think this would also help to add support for per connection settings i.e. use

Re: [bug #18136] MC wont work with new bash-3.2 propeply with all directories.

2006-11-01 Thread Leonard den Ottolander
On Wed, 2006-11-01 at 15:15 +0200, Pavel Tsekov wrote: The printf solution wouldn't be that hard to implement in fact. It may be even simpler. I can look at it. That would be nice. Thank you. Leonard. -- mount -t life -o ro /dev/dna /genetic/research

Re: [bug #18042] cannot specify port number in shell link

2006-11-01 Thread Pavel Tsekov
On Wed, 1 Nov 2006, Leonard den Ottolander wrote: On Wed, 2006-11-01 at 13:20 +0200, Pavel Tsekov wrote: IMO, it would be better if MC pops up an url specific dialog for each vfs if necessary so that the user could finer tune the connection. I think this would also help to add support for per

Re: [bug #18042] cannot specify port number in shell link

2006-11-01 Thread Leonard den Ottolander
Hello Pavel, On Wed, 2006-11-01 at 15:26 +0200, Pavel Tsekov wrote: This is not a task which requires tremendous efforts. It is just a matter of defining what we want to do and how we want to do it. And in the meantime there is an easy workaround - just set the port in ~/.ssh/config. Yes,

Re: [bug #18136] MC wont work with new bash-3.2 propeply with all directories.

2006-11-01 Thread Leonard den Ottolander
Hello Thomas, On Wed, 2006-11-01 at 08:38 -0500, Thomas Dickey wrote: One problem is that the user has to keep track (for the non-automatic workarounds) of the bash version. No. Default setting of 0 (or unset) of bash_octal_digits would fallback to option 1, which works for bash = 2.05b (in

Re: find in viewer

2006-11-01 Thread Nerijus Baliunas
Hello, could this patch please be committed to cvs (I am attaching it for your convenience)? BTW, how this patch works when two mc are running? If I search in 1st mc, then in 2nd mc, and then again in 1st mc, what will I get - last text from 1st or 2nd? I'd prefer from 1st, i.e. different mc

Re: find in viewer

2006-11-01 Thread Pavel Tsekov
On Thu, 2 Nov 2006, Nerijus Baliunas wrote: Hello, could this patch please be committed to cvs (I am attaching it for your convenience)? BTW, how this patch works when two mc are running? If I search in 1st mc, then in 2nd mc, and then again in 1st mc, what will I get - last text from 1st