Hello, Frédéric!
> Pavel (Roskin, hehe). First, about your last message:
Why hehe?
> No problems building (of course some warnings, 3 from libmcslang):
>
> /usr/local/src/CVS/mc/slang/sldisply.c: In function `SLtt_get_terminfo':
> /usr/local/src/CVS/mc/slang/sldisply.c:1784: warning: implicit declaration of
>function `g_snprintf'
> /usr/local/src/CVS/mc/slang/slerr.c: In function `SLang_doerror':
> /usr/local/src/CVS/mc/slang/slerr.c:38: warning: implicit declaration of function
>`g_snprintf'
> /usr/local/src/CVS/mc/slang/slsmg.c: In function `SLsmg_printf':
> /usr/local/src/CVS/mc/slang/slsmg.c:192: warning: implicit declaration of function
>`g_vsnprintf'
It should be easy to fix. I'll probably do it in few minutes. By the way,
it's another reason to prefer the included SLang - it uses functions from
glib.
> Well, remember my complaint about not being able to not
> download po/*.po? The only solution I found was to remove
> po/CVS/Entries. Now when I do a cvs update all I get is a
> message (the rest is updated):
CVS is a client-server system with a strong server. The server desides
what you should have on your system. This may be bad, but this is CVS, and
it's not going to change. Subversion is not ready yet, and BitKeeper is
not 100% free (although it's a topic for a separate discussion).
> Filesystem: / Device: /dev/hda1
> Free space 9345 Mb (96%) of 9688 Mb Free nodes 2537949 (99%) of 2560864
>
> Filesystem: /usr/local/src Device: /dev/hda3
> Free space 885 Mb (45%) of 1938 Mb Free nodes 408939 (79%) of 512512
>
> I know I can use df and GNU Parted :)
You can also use "ln -s" or "mount --bind".
> 3- I have a 56K modem (working like a 14.4K with my ISP), and
> can't waste bandwitch downloading all new translations or
> revisions.
I understand this concern very well. I started writing CVS Utilities on
your side of the Atlantic. However, you should download the whole stuff
only once. The changes are transmitted as patches over the net.
> I know 1.2.2 is very old but still used by some people. I
> remember John E. Davis suggesting everybody to use 1.3 (beta)
> instead because it was "stable" on Unix, before 1.4 was
> released (it took a long time with 10 1.3 releases).
I'll check it. MC includes SLang 0.99.38.
> Are you talking about that?
>
> -<-/dir----------------v>
No, I'm talking about this:
http://www.red-bean.com/~proski/history.png
> The "v"? If yes, I'm using mc (linked against S-Lang 1.4.2)
> with GNU screen (TERM=screen). If not, what's this "v"? BTW, mc
I have no idea.
> won't display colors without -c if I use screen. All other
> applications get colors (Kim, Lynx, Mutt, EPIC...).
It displays colors on RXVT. You can also add to ~/.mc/ini the following
lines:
[Colors]
color_terminals=linux,xterm,cons25,vt220,ansi
I believe that MC could do better job detecting color capabilities of the
terminal.
> Now I should ask. Are there any CVS tags for mc, like
> mc-4-5-51? I think all modules at cvs.gnome.org lack this. I
> know there are glib and glib-1-2 tags, but apparently not for
> released versions. Using mc CVS doesn't hurt, but I'm not the
> only one using CVS tags for other modules.
Run "cvs log ChangeLog". You will get a huge list of tags.
Regards,
Pavel Roskin
