From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: Article edit doesn't show all headers
Date: Mon, 21 Feb 2011 21:08:50 -0600 [thread overview]
Message-ID: <87ipwcpxz1.fsf@newsguy.com> (raw)
In-Reply-To: <87tyfwstde.fsf@gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Harry Putnam <reader@newsguy.com> writes:
>
>> In the pest when entering gnus-article-edit-mode on a message, the
>> full headers would be visible in the editing buffer.
>
> This should now be fixed in No Gnus.
I just checked again after seeing your answer.
I created new directory
I ran git clone http://git.gnus.org/gnus.git in it.
Then ran ./configure && make,
Deleted /usr/local/gnus
moved the new gnus directory to /usr/local/gnus
(Where I always keep it)
closed emacs re-restarted then started
gnus.
My version says `No Gnus v0.11'... Is that what it should say?
(I got lost trying to follow the different versioning schemes.)
I still see the behavior described in original post concering entering
gnus-article-edit-mode
next prev parent reply other threads:[~2011-02-22 3:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 2:07 Harry Putnam
2011-02-22 2:19 ` Lars Ingebrigtsen
2011-02-22 3:08 ` Harry Putnam [this message]
2011-02-22 3:19 ` Lars Ingebrigtsen
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=87ipwcpxz1.fsf@newsguy.com \
--to=reader@newsguy.com \
--cc=ding@gnus.org \
/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).