From: "Jose A. Ortega Ruiz" <jao@gnu.org>
To: ding@gnus.org
Subject: Re: funny behaviour after last message
Date: Mon, 21 Feb 2011 11:06:20 +0100 [thread overview]
Message-ID: <871v31zopv.fsf@gnu.org> (raw)
In-Reply-To: <87d3mmkuxf.fsf@gnus.org>
On Mon, Feb 21 2011, Lars Ingebrigtsen wrote:
> "Jose A. Ortega Ruiz" <jao@gnu.org> writes:
>
>> i'm using emacs-snapshot (a recent 24.0.50), which comes with a recent
>> gnus 5.13. since a couple of weeks ago, i'm experiencing what i
>> consider a misbehaviour.
>>
>> i use a three pane layout, like this:
>
> Geeze. I have no idea why that happens, but I've now added a kludge
> that seems to fix it. Can you try it, too?
Yes, it works for me too. Thanks!
jao
--
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
prev parent reply other threads:[~2011-02-21 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-20 5:26 Jose A. Ortega Ruiz
2011-02-21 2:01 ` Lars Ingebrigtsen
2011-02-21 10:06 ` Jose A. Ortega Ruiz [this message]
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=871v31zopv.fsf@gnu.org \
--to=jao@gnu.org \
--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).