From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Harald Hanche-Olsen <hanche@math.ntnu.no>
Cc: <ding@gnus.org>
Subject: Re: Problem running gnus when image is not already loaded
Date: Sat, 02 Feb 2008 18:50:10 +0100 [thread overview]
Message-ID: <v9tzkrb63x.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <20080202.170300.233589726.hanche@math.ntnu.no> (Harald Hanche-Olsen's message of "Sat, 02 Feb 2008 17:03:00 +0100 (CET)")
On Sat, Feb 02 2008, Harald Hanche-Olsen wrote:
> + Reiner Steib <reinersteib+gmane@imap.cc>:
>> When running some CVS snapshot (as 23.0.0 indicates, though I don't
>> know to which date and branch it belongs), it doesn't make sense to
>> run a version more than 2 years old.
>
> Agreed, sort of. Which is why I upgraded my sources and started a new
> build around the time I sent my report.
FYI: the unicode branch has been merged to the Emacs trunk in CVS
yesterday.
> As to why I am doing this, I found the non-unicode emacsen too
> painful to use, and the emacs-unicode-2 branch such a huge advance,
> I didn't mind using the so-called "unstable" code.
I can't find Emacs 22 (or even 21) painful to use, YMMV. But we are
getting off-topic, I think.
> In fact, I believe I have seen fewer crashes with this two year old
> CVS emacs than I ever did with most official emacs releases.
If you didn't report these crashes (in the releases), the developers
can't fix them.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2008-02-02 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080202.121924.157909693.hanche@math.ntnu.no>
2008-02-02 13:27 ` Reiner Steib
2008-02-02 16:03 ` Harald Hanche-Olsen
2008-02-02 17:50 ` Reiner Steib [this message]
2008-02-02 17:58 ` Harald Hanche-Olsen
2008-02-02 18:12 ` Reiner Steib
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=v9tzkrb63x.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=ding@gnus.org \
--cc=hanche@math.ntnu.no \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).