>> Not really. Which version of psgmlx are you using?
>> What problem(s) did you encounter with it?
> Most of the details are on the deb-doc list now. Basically, emacs24 can't
> handle the old elisp in psgmlx, hence my need for an older version of emacs.
This "hence
On Fri, 30 Sep 2016, Stefan Monnier wrote:
Not really. Which version of psgmlx are you using?
What problem(s) did you encounter with it?
Most of the details are on the deb-doc list now. Basically,
emacs24 can't handle the old elisp in psgmlx, hence my need for
an older version of
> I think (hope) the subject says it all.
Not really. Which version of psgmlx are you using?
What problem(s) did you encounter with it?
Stefan
Johann Spies writes:
> On 27 September 2016 at 23:34, Tony Baldwin
> wrote:
>
>
>
>
> Emacs?! People still use the crusty old thing?
> Perhaps he consider dumping that monstrosity and joining the rest
> of us in the 21st Century, and upgrade to a modern OS with a
>
On 27 September 2016 at 23:34, Tony Baldwin wrote:
>
> Emacs?! People still use the crusty old thing?
> Perhaps he consider dumping that monstrosity and joining the rest of us in
> the 21st Century, and upgrade to a modern OS with a proper editor, such as
> Debian 8/Jessie with Vim!"
>
>
Why so n
On Tue, Sep 27, 2016 at 5:34 PM, Tony Baldwin wrote:
> MY first thought was,"
> Emacs?! People still use the crusty old thing?
> Perhaps he consider dumping that monstrosity and joining the rest of us in
> the 21st Century, and upgrade to a modern OS with a proper editor, such as
> Debian 8/Jessie
Hi Bob.
On Tue, 27 Sep 2016, Bob Bernstein wrote:
Oh Lord I don't have time for this.
Neither do some others, and understandably so.
But it happens I do, at the moment.
Look, I thought I'd take a shot in the dark to see if just maybe
someone who knew what psgmlx was might see my Subject: a
Oh Lord I don't have time for this.
Look, I thought I'd take a shot in the dark to see if just maybe
someone who knew what psgmlx was might see my Subject: and drop
into help mode instead of wounded pride mode: "That Bernstein
fellow hurt my feelings because he asked about something about
whi
have left quite mysterious what it is you are trying to
do with psgmlx. (It may be obvious to you, but it may well not be to
anyone inclined or able to help you.) This also matters. And no,
"Trying to use this renowned, non-debian package with emacs24" is not
a good answer.
Things you
Oops. Back in the killfile for Master Brian.
--
IMPORTANT: This email is intended for the use of the individual
addressee(s) named above and may contain information that is
confidential, privileged or unsuitable for overly sensitive
persons with low self-esteem, no sense of humour or irrational
On 09/27/2016 05:19 PM, Brian wrote:
On Tue 27 Sep 2016 at 16:35:44 -0400, Bob Bernstein wrote:
I think (hope) the subject says it all.
It does: it says - I cannot be bothered to explain in any way what I
want. But I am relying on everyone to read my mind and realise how
important this is
On Tue 27 Sep 2016 at 16:35:44 -0400, Bob Bernstein wrote:
> I think (hope) the subject says it all.
It does: it says - I cannot be bothered to explain in any way what I
want. But I am relying on everyone to read my mind and realise how
important this is to me. Guesses are accepted as responses.
I think (hope) the subject says it all.
--
IMPORTANT: This email is intended for the use of the individual
addressee(s) named above and may contain information that is
confidential, privileged or unsuitable for overly sensitive
persons with low self-esteem, no sense of humour or irrational
metaph
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 UNSU
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*
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
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
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
>
t; > 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
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
Description: Digital signature
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):
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
not start it from the terminal and start from an icon or menu.
Tim Kelley
On Mon, Apr 27, 2015 at 1:49 PM, 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 o
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'
When I use aptitude to install something, it reports
errors on emacs and emacs24-nox. I says:
systemtap-mode.el:62:1:Error: Symbol's function
definition is void: cl-macroexpand-all
$ sudo aptitude install iamerican-insane
...
The following NEW packages will be installed:
iame
* 2010-03-08 00:33 (-0500), Stefan Monnier wrote:
> Yes, it's a real shame. We're also still waiting for Debian to put
> Emacs-24 in unstable at least, so we can grab the source and release
> it. But we've been waiting for so long that we're losing hope. We may
> end up having to write the code ou
> Anyone know when emacs24 will be in Debian squeeze? The latest they
> have is emacs23 :(
Yes, it's a real shame. We're also still waiting for Debian to put
Emacs-24 in unstable at least, so we can grab the source and release it.
But we've been waiting for so long that w
On 3/7/2010 4:51 PM, Zachary Uram wrote:
Anyone know when emacs24 will be in Debian squeeze? The latest they
have is emacs23 :(
What is so desirable about v.24?
Mark Allums
(a confirmed vi man)
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of
On Sun, Mar 07, 2010 at 05:51:00PM -0500, Zachary Uram wrote:
> Anyone know when emacs24 will be in Debian squeeze? The latest they
> have is emacs23 :(
>
Emacs 23.1 is the current release and it is in squeeze. A slightly higher
version of 23.1 is in sid.
http://www.gnu.org/softw
Anyone know when emacs24 will be in Debian squeeze? The latest they
have is emacs23 :(
Zach
<>< http://www.fidei.org ><>
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lis
42 matches
Mail list logo
