From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: Oort Gnus v0.17 is released
Date: Mon, 31 Mar 2003 16:20:08 -0600 [thread overview]
Message-ID: <un0jbmb53.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <m3fzp3qjuy.fsf@peorth.intersystems.com>
Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> * Lars Magne Ingebrigtsen <larsi@gnus.org> on Mon, 31 Mar 2003
> | Probably a couple more Oorts before Gnus 5.10 on May 1st.
>
> v0.17 is still improperly storing gnus-format-specs in .newsrc.eld. v0.15
> and previous kept the lisp form as a single line; v0.16 and v0.17 split it
> into several lines in a way that causes the setq to break when the eld
> file is loaded after killing Emacs and starting a new session.
>
> I have not yet figured out how to fix this behaviour.
It's possible that I introduced this problem. However .newsrc.eld,
even split across several lines, works fine for me (and apparently
most since the linchmob hasn't found me :) ). Can you be more
specific concerning the problems that you are seeing? In my
.newsrc.eld, the line splits occur were newline characters appear in
character strings. Are you needing to convert these back to '\n'
codes to make your setq work?
Kevin
next prev parent reply other threads:[~2003-03-31 22:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 18:09 Lars Magne Ingebrigtsen
2003-03-31 21:58 ` Stainless Steel Rat
2003-03-31 22:20 ` Kevin Greiner [this message]
2003-03-31 22:34 ` Jack Twilley
2003-04-01 2:07 ` Stainless Steel Rat
2003-04-01 5:11 ` Kevin Greiner
2003-04-01 15:44 ` Stainless Steel Rat
2003-04-01 16:07 ` Stainless Steel Rat
2003-04-01 16:50 ` Kevin Greiner
2003-04-01 19:04 ` Stainless Steel Rat
2003-04-03 2:51 ` Kevin Greiner
2003-04-04 3:22 ` Stainless Steel Rat
2003-04-01 2:43 ` Lars Magne Ingebrigtsen
2003-03-31 22:53 ` Vasily Korytov
2003-04-01 2:43 ` Lars Magne Ingebrigtsen
2003-04-02 10:20 ` Zack Weinberg
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=un0jbmb53.fsf@xpediantsolutions.com \
--to=kgreiner@xpediantsolutions.com \
/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).