Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

jessie: how to suppress emacs24 warnings

123 views
Skip to first unread message

Juha Heinanen

unread,
Apr 27, 2015, 3:00:04 PM4/27/15
to
after upgrading to jessie that came with emacs24, i get the warnings
below to terminal window each time i start emacs in x11 environment.
any hints on how to get rid of them?

-- juha

(emacs:12957): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:57:17: Theming engine 'unico' not found

(emacs:12957): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:289:20: Not using units is deprecated. Assuming 'px'.

(emacs:12957): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:323:20: Not using units is deprecated. Assuming 'px'.

(emacs:12957): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:1828:20: Not using units is deprecated. Assuming 'px'.

(emacs:12957): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:1845:21: Not using units is deprecated. Assuming 'px'.

(emacs:12957): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:1861:20: Not using units is deprecated. Assuming 'px'.

(emacs:12957): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:2146:20: Not using units is deprecated. Assuming 'px'.

(emacs:12957): Gtk-WARNING **: Theme parsing error: gtk-widgets-backdrop.css:16:20: Not using units is deprecated. Assuming 'px'.

(emacs:12957): Gtk-WARNING **: Theme parsing error: gtk-widgets-backdrop.css:93:20: Not using units is deprecated. Assuming 'px'.

(emacs:12957): Gtk-WARNING **: Theme parsing error: gtk-widgets-backdrop.css:183:20: Not using units is deprecated. Assuming 'px'.

(emacs:12957): Gtk-WARNING **: Theme parsing error: gtk-widgets-backdrop.css:503:20: Not using units is deprecated. Assuming 'px'.

(emacs:12957): Gtk-WARNING **: Theme parsing error: gtk-widgets-backdrop.css:850:20: Not using units is deprecated. Assuming 'px'.

(emacs:12957): Gtk-WARNING **: Theme parsing error: gtk-widgets-backdrop.css:925:20: Not using units is deprecated. Assuming 'px'.

(emacs:12957): Gtk-WARNING **: Theme parsing error: gtk-widgets-backdrop.css:941:20: Not using units is deprecated. Assuming 'px'.

(emacs:12957): Gtk-WARNING **: Theme parsing error: gtk-widgets-backdrop.css:957:20: Not using units is deprecated. Assuming 'px'.

(emacs:12957): Gtk-WARNING **: Theme parsing error: gtk-widgets-backdrop.css:1012:21: Not using units is deprecated. Assuming 'px'.

(emacs:12957): Gtk-WARNING **: Theme parsing error: gtk-widgets-backdrop.css:1020:21: Not using units is deprecated. Assuming 'px'.

(emacs:12957): Gtk-WARNING **: Theme parsing error: gtk-widgets-backdrop.css:1034:21: Not using units is deprecated. Assuming 'px'.

(emacs:12957): Gtk-WARNING **: Theme parsing error: gtk-widgets-backdrop.css:1103:21: Not using units is deprecated. Assuming 'px'.

(emacs:12957): Gtk-WARNING **: Theme parsing error: gtk-widgets-backdrop.css:1237:20: Not using units is deprecated. Assuming 'px'.

(emacs:12957): Gtk-WARNING **: Theme parsing error: gnome-panel.css:94:21: Not using units is deprecated. Assuming 'px'.

(emacs:12957): Gtk-WARNING **: Theme parsing error: nautilus.css:18:18: Not using units is deprecated. Assuming 'px'.

(emacs:12957): Gtk-WARNING **: Theme parsing error: nautilus.css:18:20: Not using units is deprecated. Assuming 'px'.

(emacs:12957): Gtk-WARNING **: Theme parsing error: nautilus.css:81:20: Not using units is deprecated. Assuming 'px'.

(emacs:12957): Gtk-WARNING **: Theme parsing error: nautilus.css:86:20: Not using units is deprecated. Assuming 'px'.

(emacs:12957): Gtk-WARNING **: Theme parsing error: nautilus.css:145:20: Not using units is deprecated. Assuming 'px'.


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/21822.33998....@tutpro.com

Tim Kelley

unread,
Apr 27, 2015, 3:10:04 PM4/27/15
to

If you just use the console emacs, you can install the emacs-nox version of 24. In anycase, they’re just warnings, and can be ignored. It’s just stating something some other packager did was deprecated but still functional .. you can start emacs with emacs >/dev/null 2>&1 if you like, or not start it from the terminal and start from an icon or menu.

​

Tim Kelley

Juha Heinanen

unread,
Apr 27, 2015, 3:20:07 PM4/27/15
to
Tim Kelley writes:

> If you just use the console emacs, you can install the emacs-nox version of
> 24.

In this case, i used x11 emacs, but started it from console.

> In anycase, they’re just warnings, and can be ignored.

Yes, I know, but the warnings consume the whole page of the terminal
window and I cannot anymore see, what was there without scrolling back,
which is annoying.

> It’s just
> stating something some other packager did was deprecated but still
> functional .. you can start emacs with emacs >/dev/null 2>&1 if you like,
> or not start it from the terminal and start from an icon or menu.

Typing emacs >/dev/null 2>&1 is too cumbersome and starting from menu
looses the directory where I am. For example, if the current dir has a
file that I want to edit, I just used to type

emacs file

but now I get all the garbage to the window which is not good.

Is there anything that can be done to get rid of those warnings? Which
package the bug lies? Is there any hope that the bugs are fixed before
the next Debian release?

-- Juha


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/21822.35589....@tutpro.com

Erwan David

unread,
Apr 27, 2015, 3:40:04 PM4/27/15
to
Le 27/04/2015 21:16, Juha Heinanen a écrit :
> Tim Kelley writes:
>
>> If you just use the console emacs, you can install the emacs-nox version of
>> 24.
> In this case, i used x11 emacs, but started it from console.
>
>> In anycase, they’re just warnings, and can be ignored.
> Yes, I know, but the warnings consume the whole page of the terminal
> window and I cannot anymore see, what was there without scrolling back,
> which is annoying.
>
>> It’s just
>> stating something some other packager did was deprecated but still
>> functional .. you can start emacs with emacs >/dev/null 2>&1 if you like,
>> or not start it from the terminal and start from an icon or menu.
> Typing emacs >/dev/null 2>&1 is too cumbersome and starting from menu
> looses the directory where I am. For example, if the current dir has a
> file that I want to edit, I just used to type
>
> emacs file
>
> but now I get all the garbage to the window which is not good.
>
> Is there anything that can be done to get rid of those warnings? Which
> package the bug lies? Is there any hope that the bugs are fixed before
> the next Debian release?

You may also use lucid-emacs which works well in X11 and does nit have
those warnings since it does not use GTK. (and has same functionality).


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/553E8FD...@rail.eu.org

Curt

unread,
Apr 27, 2015, 4:00:05 PM4/27/15
to
On 2015-04-27, Juha Heinanen <j...@tutpro.com> wrote:
>
> Typing emacs >/dev/null 2>&1 is too cumbersome and starting from menu

Create an alias.


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/slrnmjt52l...@einstein.electron.org

Tim Kelley

unread,
Apr 27, 2015, 4:00:05 PM4/27/15
to
Well, typing it is cumbersome so you can do in ~/.bash_aliases or ~/.bashrc

alias emacs='emacs > /dev/null 2>&1'

I agree though, that is annoying, and a lot of GTK programs do that. And sending the output to null isn't really the right answer, since you'll miss actual errors that are important. As far as I can tell, it's a compiled flag on gtk, so filing a bug against gtk is probably the best thing to do. You could rebuild the gtk deb from the source deb and change that and install it too, if you want to do that.

Tim Kelley

Cláudio E. Elicker

unread,
Apr 27, 2015, 5:10:04 PM4/27/15
to
On Mon, 27 Apr 2015 21:49:50 +0300
Juha Heinanen <j...@tutpro.com> wrote:

> after upgrading to jessie that came with emacs24, i get the warnings
> below to terminal window each time i start emacs in x11 environment.
> any hints on how to get rid of them?
>
> -- juha
>
> (emacs:12957): Gtk-WARNING **: Theme parsing error:
> gtk-widgets.css:57:17: Theming engine 'unico' not found
>
> (emacs:12957): Gtk-WARNING **: Theme parsing error:
> gtk-widgets.css:289:20: Not using units is deprecated. Assuming 'px'.
>

...


Are you using you old emacs23 .emacs file?

Try to launch emacs with the -q switch.
If the warnings disappear, it's just a matter of finding the offending
lines in your .emacs file.

I guess it is some theme configuration. If you are (was) using the
emacs23 color-theme mode, this link can be useful:
https://github.com/emacs-jp/replace-colorthemes


--
EMACS is my operating system; Linux is my device driver.


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20150427180...@speedy.parsec

Bob Proulx

unread,
Apr 27, 2015, 6:50:05 PM4/27/15
to
Erwan David wrote:
> Juha Heinanen a écrit :
> > Is there anything that can be done to get rid of those warnings? Which
> > package the bug lies? Is there any hope that the bugs are fixed before
> > the next Debian release?

To fix the bugs associated with those Gtk-WARNING messages it would be
necessary to roll up the sleeves, break out the editor, source code,
and compilers, and start working on the GTK libraries. There are
seemingly endless bugs there.

> You may also use lucid-emacs which works well in X11 and does nit have
> those warnings since it does not use GTK. (and has same functionality).

+1 FTW! Except that it is spelled "emacs-lucid". I am using the
emacs-lucid to avoid some bugs in the GTK+ libraries.

# apt-get install emacs24-lucid

Bob
signature.asc

Cláudio E. Elicker

unread,
Apr 27, 2015, 7:20:04 PM4/27/15
to
Strange, I do not see these warnings here.



--
EMACS is my operating system; Linux is my device driver.


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20150427201...@speedy.parsec

Tim Kelley

unread,
Apr 27, 2015, 7:30:05 PM4/27/15
to
As I understand it, it is generally considered unprofessional to have your application print warnings.

Tim Kelley

Vincent Lefevre

unread,
Apr 27, 2015, 8:50:03 PM4/27/15
to
On 2015-04-27 14:57:05 -0500, Tim Kelley wrote:
> Well, typing it is cumbersome so you can do in ~/.bash_aliases or ~/.bashrc
>
> alias emacs='emacs > /dev/null 2>&1'
>
> I agree though, that is annoying, and a lot of GTK programs do that. And
> sending the output to null isn't really the right answer, since you'll miss
> actual errors that are important.

I completely agree. I would never do that. Writing a shell function
that greps out the Gtk-WARNING lines may be better.

> As far as I can tell, it's a compiled flag on gtk, so filing a bug
> against gtk is probably the best thing to do. You could rebuild the
> gtk deb from the source deb and change that and install it too, if
> you want to do that.

Are these messages output by the GTK library itself or reported to
Emacs or output by emacs itself?

Having output in a library (except for output functions, of course) is
bad practice (possibly except critical errors, like assertion failure
or memory corruption, which could mean an imminent crash or possible
data loss). Errors should be reported to the caller.

--
Vincent Lefèvre <vin...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20150428004...@xvii.vinc17.org

The Wanderer

unread,
Apr 27, 2015, 9:00:04 PM4/27/15
to
On 04/27/2015 at 08:44 PM, Vincent Lefevre wrote:

> On 2015-04-27 14:57:05 -0500, Tim Kelley wrote:
>
>> Well, typing it is cumbersome so you can do in ~/.bash_aliases or
>> ~/.bashrc
>>
>> alias emacs='emacs > /dev/null 2>&1'
>>
>> I agree though, that is annoying, and a lot of GTK programs do
>> that. And sending the output to null isn't really the right answer,
>> since you'll miss actual errors that are important.
>
> I completely agree. I would never do that. Writing a shell function
> that greps out the Gtk-WARNING lines may be better.

Not ideal, though, since there are (as I understand matters) often but
not necessarily always blank lines in between these Gtk-WARNING lines.
So either you cut out just the WARNING lines and still have scrolliness
because of the blank lines making it through, or you snip out the
adjacent lines and risk killing other information. (Or you make your
script potentially quite a bit more complicated.)

>> As far as I can tell, it's a compiled flag on gtk, so filing a bug
>> against gtk is probably the best thing to do. You could rebuild
>> the gtk deb from the source deb and change that and install it too,
>> if you want to do that.
>
> Are these messages output by the GTK library itself or reported to
> Emacs or output by emacs itself?
>
> Having output in a library (except for output functions, of course)
> is bad practice (possibly except critical errors, like assertion
> failure or memory corruption, which could mean an imminent crash or
> possible data loss). Errors should be reported to the caller.

Given the sheer number of different programs which I've seen output them
(this includes iceweasel and icedove), I rather suspect they're output
by the library itself. I think I researched this more specifically once,
but if so I forget the details.

--
The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw

signature.asc

The Wanderer

unread,
Apr 27, 2015, 9:30:04 PM4/27/15
to
On 04/27/2015 at 09:24 PM, Vincent Lefevre wrote:

> On 2015-04-27 20:52:15 -0400, The Wanderer wrote:
>
>> On 04/27/2015 at 08:44 PM, Vincent Lefevre wrote:
>>
>>> I completely agree. I would never do that. Writing a shell
>>> function that greps out the Gtk-WARNING lines may be better.
>>
>> Not ideal, though, since there are (as I understand matters) often
>> but not necessarily always blank lines in between these Gtk-WARNING
>> lines. So either you cut out just the WARNING lines and still have
>> scrolliness because of the blank lines making it through, or you
>> snip out the adjacent lines and risk killing other information. (Or
>> you make your script potentially quite a bit more complicated.)
>
> Yes, one can write a small script that also removes blank lines that
> come after a Gtk-WARNING line.

My brief research seems to indicate the blank line is actually printed
_before_ the GTK-sourced line. Not sure how much harder that would make
things, just offhand.
signature.asc

Vincent Lefevre

unread,
Apr 27, 2015, 9:30:04 PM4/27/15
to
On 2015-04-27 20:52:15 -0400, The Wanderer wrote:
> On 04/27/2015 at 08:44 PM, Vincent Lefevre wrote:
> > I completely agree. I would never do that. Writing a shell function
> > that greps out the Gtk-WARNING lines may be better.
>
> Not ideal, though, since there are (as I understand matters) often but
> not necessarily always blank lines in between these Gtk-WARNING lines.
> So either you cut out just the WARNING lines and still have scrolliness
> because of the blank lines making it through, or you snip out the
> adjacent lines and risk killing other information. (Or you make your
> script potentially quite a bit more complicated.)

Yes, one can write a small script that also removes blank lines that
come after a Gtk-WARNING line.

One just has to hope that no full buffering is done when stderr is
piped to a filter.

> > Are these messages output by the GTK library itself or reported to
> > Emacs or output by emacs itself?
> >
> > Having output in a library (except for output functions, of course)
> > is bad practice (possibly except critical errors, like assertion
> > failure or memory corruption, which could mean an imminent crash or
> > possible data loss). Errors should be reported to the caller.
>
> Given the sheer number of different programs which I've seen output them
> (this includes iceweasel and icedove), I rather suspect they're output
> by the library itself. I think I researched this more specifically once,
> but if so I forget the details.

This is also what I suspect.

--
Vincent Lefèvre <vin...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20150428012...@xvii.vinc17.org

Nate Bargmann

unread,
Apr 27, 2015, 9:30:05 PM4/27/15
to
"Here" those annoying messages are sent to ~/.xsession-errors which has
been open about 9 days and is approaching 58 MiB in size. To be fair,
most of the garbage is not coming from glib/gtk but rather from Firefox
(I am not using Iceweasel) complaining about javascript this or that.

Oh well, "disk space is cheap"...

- Nate

--

"The optimist proclaims that we live in the best of all
possible worlds. The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/2015042801...@n0nb.us

Vincent Lefevre

unread,
Apr 27, 2015, 9:40:03 PM4/27/15
to
On 2015-04-27 20:23:48 -0500, Nate Bargmann wrote:
> "Here" those annoying messages are sent to ~/.xsession-errors which has
> been open about 9 days and is approaching 58 MiB in size. To be fair,
> most of the garbage is not coming from glib/gtk but rather from Firefox
> (I am not using Iceweasel) complaining about javascript this or that.

AFAIK, these messages are simply sent to the standard error stream.
So, it depends on how applications are started. If started in a
text terminal, then these messages appear in the terminal since this
is where stderr goes by default. If started from the window manager
or desktop environment, then they probably do nothing special about
stderr, i.e. error messages typically go to the same place, which
may be the ~/.xsession-errors file.

--
Vincent Lefèvre <vin...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20150428012...@xvii.vinc17.org

Vincent Lefevre

unread,
Apr 27, 2015, 9:40:03 PM4/27/15
to
On 2015-04-27 21:29:07 -0400, The Wanderer wrote:
> On 04/27/2015 at 09:24 PM, Vincent Lefevre wrote:
> > Yes, one can write a small script that also removes blank lines that
> > come after a Gtk-WARNING line.
>
> My brief research seems to indicate the blank line is actually printed
> _before_ the GTK-sourced line. Not sure how much harder that would make
> things, just offhand.

Perhaps, but it may be better to filter out the one that it after. The
reason is that you don't know in advance if a blank line is part of a
Gtk-WARNING. So, you would have to delay its printing. Probably not
much a problem, but it's a bit annoying to introduce delay for a
process that may actually not output any Gtk-WARNING line at all.

--
Vincent Lefèvre <vin...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20150428013...@xvii.vinc17.org

Don Armstrong

unread,
Apr 28, 2015, 2:10:04 PM4/28/15
to
On Mon, 27 Apr 2015, Tim Kelley wrote:
> Well, typing it is cumbersome so you can do in ~/.bash_aliases or ~/.bashrc
>
> alias emacs='emacs > /dev/null 2>&1'

I actually use the following:

#!/bin/sh
# fork and forget == faf
("$@" >/dev/null 2>&1 &)

as faf in ~/bin[1]

so you can do things like faf emacs; and faf evince; etc. You can also
fix up the completion in bash/zsh so that completion works as usual
after faf.

1: http://git.donarmstrong.com/?p=bin.git;a=blob;f=faf;hb=HEAD
--
Don Armstrong http://www.donarmstrong.com

Given that the odds of a miracle are one in one million, and events
which could be a miracle happen every second, the odds of not seeing a
miracle in a month are less than 8 in 100. Clearly miracles are not
all that miraculous.


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/20150428180...@teltox.donarmstrong.com

Juha Heinanen

unread,
Apr 30, 2015, 8:20:05 AM4/30/15
to
Cláudio E. Elicker writes:

> Are you using you old emacs23 .emacs file?

My .emacs.d/init.el is the same I have used with emacs23.

> Try to launch emacs with the -q switch.
> If the warnings disappear, it's just a matter of finding the offending
> lines in your .emacs file.

Thanks for your suggestion, but unfortunately I get the warnings also
with -q option.

> EMACS is my operating system; Linux is my device driver.

Good line. I myself have been using emacs since my university bought
DEC-20 in the late 1970s.

-- Juha


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/21826.7357....@tutpro.com

Juha Heinanen

unread,
Apr 30, 2015, 8:30:07 AM4/30/15
to
Nate Bargmann writes:

> "Here" those annoying messages are sent to ~/.xsession-errors which has
> been open about 9 days and is approaching 58 MiB in size. To be fair,
> most of the garbage is not coming from glib/gtk but rather from Firefox
> (I am not using Iceweasel) complaining about javascript this or that.

Thanks for the pointer. I just checked mine:

$ ls -ls .xsession-errors
15967456 -rw------- 1 jh jh 16350667713 Apr 30 14:57 .xsession-errors

I'll add to my openbox/autostart a line to delete the file.

-- Juha


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/21826.7664....@tutpro.com

Juha Heinanen

unread,
May 1, 2015, 7:00:04 AM5/1/15
to
Bob Proulx writes:

> +1 FTW! Except that it is spelled "emacs-lucid". I am using the
> emacs-lucid to avoid some bugs in the GTK+ libraries.
>
> # apt-get install emacs24-lucid

Thanks for the tip. After installing emacs24-lucid, the warnings
disappeared, but I got a new one:

$ emacs24-lucid
Warning: Cannot convert string "Monospace 10" to type FontStruct

I have defined in .Xresources

Emacs*font: Monospace 10

and that used to work in emacs24.

-- Juha


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/21827.23571....@tutpro.com

Bob Proulx

unread,
May 1, 2015, 4:10:04 PM5/1/15
to
Juha Heinanen wrote:
> Thanks for the tip. After installing emacs24-lucid, the warnings
> disappeared, but I got a new one:
>
> $ emacs24-lucid
> Warning: Cannot convert string "Monospace 10" to type FontStruct
>
> I have defined in .Xresources
>
> Emacs*font: Monospace 10
>
> and that used to work in emacs24.

Fonts! Ugh. We get to discuss fonts. Do I want to open that
discussion up? I am not an expert in fonts. But I didn't think that
"Monospace 10" was a valid font name.

Is that equivalent to 6x10 or 10x20? Try one of these:

Emacs*font:6x10

That will probably work for you and you might be happy at that point.
But let me try to convince you to try a unicode font.

In the old days we would have used fixed width fonts like some of these:

5x7
6x10
7x13
9x15
10x20
12x24

But those are US-ASCII fonts only. All of the non-ascii characters
can't be rendered in them. These days UTF-8 is everywhere. So
instead of a fixed us-ascii font these days it is really much better
to use a unicode font. One of the ISO-10646 fonts. Try an ISO10646
font and then you will have all of the accents and umlauts working.

I like the efonts. Fonts are such a personal preference that there is
nothing more to be done than just to try fonts and decide on what you
like for yourself.

apt-get install xfonts-efont-unicode xfonts-efont-unicode-ib

Then you can configure emacs to use them this way:

XTerm*Font: -efont-fixed-medium-r-normal-*-16-*-*-*-*-*-iso10646-1
XTerm*Font2: -efont-fixed-medium-r-normal-*-12-*-*-*-*-*-iso10646-1
XTerm*Font3: -efont-fixed-medium-r-normal-*-14-*-*-*-*-*-iso10646-1
XTerm*Font4: -efont-fixed-medium-r-normal-*-16-*-*-*-*-*-iso10646-1
XTerm*Font5: -misc-fixed-medium-r-normal--18-*-*-*-*-*-iso10646-1
XTerm*Font6: -efont-fixed-medium-r-normal-*-24-*-*-*-*-*-iso10646-1

You would probably also like these fonts too.

xfonts-unifont xfonts-terminus-dos xfonts-terminus-oblique xfonts-terminus

You can browse the names of fonts using xlsfonts.

xlsfonts | less
xlsfonts | grep fixed-medium.*iso10646 | less

I am far from a font expert. However I know what I like and people
who are really into fonts usually like things I don't like. If you
have been using a monospace 10 point font then you probably want one
of the fixed medium r normal fonts just like I do.

Bob
signature.asc

Juha Heinanen

unread,
May 2, 2015, 1:20:04 AM5/2/15
to
Bob Proulx writes:

> Fonts! Ugh. We get to discuss fonts. Do I want to open that
> discussion up? I am not an expert in fonts. But I didn't think that
> "Monospace 10" was a valid font name.

Monospace is font family name that (I think) is mapped to DejaVu Sans
Mono by /etc/fonts/conf.avail/57-dejavu-sans-mono.conf.

Anyway, I replaced my .Xresource font definition with

(set-frame-font "-unknown-DejaVu Sans Mono-normal-normal-normal-*-13-*-*-*-m-0-iso10646-1")

in my emacs init file and emacs24-lucid is happy with that.

-- Juha


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/21828.24028....@tutpro.com
0 new messages