Tuesday, December 1, 2015

Re: vim font issue

Hi Reid!

On Di, 01 Dez 2015, Reid Thompson wrote:

> On Tue, 2015-12-01 at 22:05 +0100, Christian Brabandt wrote:
> > Hi Charles!
> >
> > On Di, 01 Dez 2015, Charles E Campbell wrote:
> >
> > > Christian Brabandt wrote:
> > > > Hi,
> > > > can someone enlighten me, how the configure vim to display the attached
> > > > text file correctly?
> > > >
> > > > For me, it does not display correctly under Windows, neither on Unix as
> > > > Gvim. For the terminal gnome-terminal (3.14.1) vim seems to display the
> > > > font almost correctly.
> > > >
> > > > I attach a screenshot on how it looks here locally (upper application is
> > > > iceweasel displaying the 2html'ed file, in the middle is gtk2 gvim (font
> > > > seems to be Monospace Regular 10) 7.4.942 and at the bottom is the
> > > > display in Gnome Terminal.
> > > >
> > > > Also what options do I need (or fonts?)
> > > >
> > > > BTW: What would be suitable fonts for use on windows  guifontwide
> > > > setting? I read the help, but I am not sure how to set this correctly.
> > > > Setting guifontwide=* does not work there.
> > > >
> > > Hi, Chris:
> > >
> > > I'm sure I can't help you, because it sounds like its a Windows font
> > > installing problem.  However, I wasn't really able to get a good copy of
> > > your "txt" file, either -- something seems to be trying to "helpfully"
> > > interpret it (I use seamonkey, did a save-as, and got
> > >
> > > (͡° ͜ʖ ͡°)
> > >
> > > which doesn't particularly resemble any of the screenshots you have).  I
> > > suggest using gzip on the file and attaching that -- because mimencode
> > > knows to leave gzip'd contents alone no matter how odd.
> >
> > Okay, please try again with the attached and gzip'ed file.
> >
> > Best,
> > Christian
> > --
> > Ich bin der Überzeugung, daß es kaum jemanden gibt, dessen Intimleben
> > die Welt nicht in Staunen und Horror versetzte, wenn es übers Radio
> > gesendet werden würde.
> >  -- William Somerset Maugham
> >
> > --
> opening the gzip'd file in gvim on my box gives list filetype  utf-8 unix
> and the text and 'image' below, which is rendered slightly differently
> in gvim vs in the evolution composer window (see attached png of gvim
> rendering ColPop.png and vim rendering ColPop1.png which is also slightly
> different and evo composer rendering ColPop2.png )

I think you attached the wrong ColPop.png.


Best,
Christian
--
Wir sind, um es einmal so zu formulieren, eigentlich nur die
Neandertaler von morgen.
-- Hoimar von Ditfurth

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments: