[Pkg-mc-devel] MC 4.8.1-3

Andreas Tille andreas at an3as.eu
Thu Mar 15 08:36:21 UTC 2012


On Wed, Mar 14, 2012 at 10:32:18AM +1100, Dmitry Smirnov wrote:
> > 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.

I think when I wrote my firt mail I did set this as well and just forgot
now.  I can confirm that gnome-terminal now shows the double lined font
to separate both mc panels but xterm as well as xfterm4 don't.

> > 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.

Sure - I know this in principle.  But pressing F? keys works for me via
backbone and I *always* try F10 before noticing that this does not work.
:-(

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

I do not want to turn this into a terminal preference thread which does
make as much sense as an Emacs vs Vi thread.  I learned gnome-terminal
is not for me and thus it seems those 256 skins are not for me as well
because they relay on those double lines which for whatever reasons are
not displayed in the terminal I'm using.

> > ║/.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.

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

How can I check / enforce this?  I'm using the following string
in my /etc/X11/Xresources/xterm:

xterm*font: -*-fixed-medium-r-normal-*-15-*-*-*-*-*-iso8859-*

If this could be enhanced I would like to know this.  If it turns out
that the user needs to adjust the terminal configuration a bit than we
should mention this inside the according README which describes the
skins.

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

Sounds reasonable and I actually intended to suggest this.  But as I
said above we should probably accompany this with hints how to make
soure the original ones will work.  I did not dived very deeply into X
configuration issues - just made sure that if I fire up a xterm via key
bindings it will occupy exactly one quarter of my screen and is using a
perfectly readable font.  I'd like to know how to enhance this to get
a font which profits from advanced mc features.

Kind regards

      Andreas.

-- 
http://fam-tille.de



More information about the Pkg-mc-devel mailing list