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/5
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 t
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-luci
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 javascri
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 sugge
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 f
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_ th
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
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.
>>
>> N
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) oft
"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, "dis
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
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 a
As I understand it, it is generally considered unprofessional to have your
application print warnings.
Tim Kelley
On Mon, Apr 27, 2015 at 5:39 PM, Bob Proulx wrote:
> Erwan David wrote:
> > Juha Heinanen a écrit :
> > > Is there anything that can be done to get rid of those warnings? Which
>
On Mon, 27 Apr 2015 16:39:56 -0600
Bob Proulx wrote:
> 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 f
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
n
On Mon, 27 Apr 2015 21:49:50 +0300
Juha Heinanen 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 parsi
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. A
On 2015-04-27, Juha Heinanen wrote:
>
> Typing emacs >/dev/null 2>&1 is too cumbersome and starting from menu
Create an alias.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.
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
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
windo
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
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
(ema
23 matches
Mail list logo
