From: Richard Stallman <rms@gnu.org>
Cc: jan.h.d@swipnet.se
Subject: Re: recent emacs font problems?
Date: Tue, 10 Jun 2003 20:24:04 -0400 [thread overview]
Message-ID: <E19PtPI-0006PQ-Fj@fencepost.gnu.org> (raw)
In-Reply-To: <5xwufun5uf.fsf@kfs2.cua.dk> (storm@cua.dk)
> I cant really grasp the problem that lead to this change from the
> comment above, so if anyone can describe a case for the original
> problem, I can try and make this work.
Here is what RMS said about the exact same fix some days ago; please
read the previous articles in this thread for a discussion on this
subject:
RMS> That is not correct. It would bring back a bug I fixed recently. I
RMS> think it was the following bug.
We need to understand what's going on in the two different cases
enough to figure out a way to distinguish them and do the right thing
for both.
next prev parent reply other threads:[~2003-06-11 0:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-09 12:06 recent emacs font problems? Jan D.
2003-06-10 0:17 ` Kim F. Storm
2003-06-10 18:18 ` Jan D.
2003-06-12 14:03 ` Richard Stallman
2003-06-12 16:29 ` Jan D.
2003-06-13 22:03 ` Richard Stallman
2003-06-26 21:32 ` Jan D.
2003-06-26 22:20 ` Sam Steingold
2003-07-07 21:51 ` David Abrahams
2003-07-07 22:16 ` Jason Rumney
2003-07-08 13:40 ` Sam Steingold
2003-07-09 1:31 ` Miles Bader
2003-07-11 20:33 ` David Abrahams
2003-07-11 21:51 ` Jason Rumney
2003-06-11 0:24 ` Richard Stallman [this message]
2003-06-15 15:59 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2003-05-28 1:14 Miles Bader
2003-05-28 4:25 ` Kenichi Handa
2003-05-28 5:14 ` John Paul Wallington
2003-05-28 6:56 ` Miles Bader
2003-05-28 10:16 ` John Paul Wallington
2003-05-28 13:55 ` Richard Stallman
2003-05-30 0:47 ` Kim F. Storm
2003-05-30 17:13 ` Richard Stallman
2003-05-28 5:13 ` Karl Eichwalder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E19PtPI-0006PQ-Fj@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=jan.h.d@swipnet.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.