[Pkg-mc-devel] MC 4.8.1-3

[Dmitry Smirnov]

Hi Andreas,

On Tue, 13 Mar 2012 21:35:31 Andreas Tille wrote:
> > Because you didn't reply, I'm still wondering what font you have by
> > default in your terminal application.
> 
> Seems I have missed some message.  Did you somehow responded to
> 
>   
> http://lists.alioth.debian.org/pipermail/pkg-mc-devel/2012-March/002593.ht
> ml
> 

Yes I did but now I see my message didn't make it to archive, probably because 
I attached a little screenshot. Sorry.


> at least the archive does not show anything and my SPAM filter might
> have catched a private mail.

That's not the case because I relied to mailing list only.
Sorry for troubles, I replied again so hopefully you'll see what I wrote at 2 
of March.


> 
> If it turns out that my personal setup I'd go for an upload.  However, I
> tried again and now I get a red window
> 
>  │ Unable to use 'modarin256' skin with 256 colors support │
>  │ on non-256 colors terminal.                             │
>  │ Default skin has been loaded                            │
> 

I added "TERM=xterm-256color" to my .bashrc to make it work.


> Usually I'm using plain xterm and for the sake of testing I tried
> xfterm4 as well as gnome-terminal (which terribly bores me anyway
> because of eating F10).  I've got the same for every terminal.

MC have more that one way to do things - when F10 is not available (and I've 
seen terminals without F* keys at all) you can use alternative Alt+0 shortcut 
which have the same effect as F10 in MC.

Usually those terminal applications can be reconfigured in regards to F10.


> 
> However, when reading my mail in the archive I observed a very
> starnge thing:  Where I have seen just "nothing" (=blank) the
> HTML view prints a double line which is probably the perfectly
> intended behaviour.  So in my terminal I see:
> 
>  /.audacity-data              │   4096│21. Feb 15:17  /.audacity-data      
>        │   4096│21. Feb 15:17
> 
> (I edited afterwards!!) instead of
> 
> ║/.audacity-data              │   4096│21. Feb 15:17║║/.audacity-data      
>        │   4096│21. Feb 15:17║
> 
> (which looks perfectly the same for me in my terminal).  So this is
> obviosely a missing font display - the question is: which one?  For me
> this might be an extra "Suggests" for the font package we need to find
> out.  However, I'd regard this as a wishlist issue - no real need to
> delay an upload of 4.8.1-3 if we do not find a clue immediately.

I think it's a bit beyond missing font because it may be a particular 
characters missed in font or just not the right font configured in terminal 
application.

My term app. uses "DejaVu Sans Mono" which works just as expected.

Your reply inspired me to introduce thin variants of new skins - you can find 
'em in repository. What do you think?


All the best,
Dmitry.