Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: draft group weirdness
Date: Wed, 18 May 2011 07:39:17 -0400	[thread overview]
Message-ID: <87ipt8dyqi.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87sjtw40jh.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Wed, 06 Apr 2011 09:43:30 +0800")

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> On Wed, Apr 06 2011, Lars Magne Ingebrigtsen wrote:
>
>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>
>>> I've been having a lot of trouble with the drafts group recently. I
>>> save drafts, go back into the drafts folder, hit 'e' to edit a message,
>>> and it asks me for a file to save into.
>>
>> That's bizarre.  (setq debug-on-quit t) and `C-g' when it prompts, so
>> that we can see what function you're calling with `e'.

I think I found the culprit here: window configuration. Doesn't make a
whole lot of sense, but neither did the error to begin with. I had a
three-pane thing going on, and I recently got rid of it because it was
such a pain to manually move point to the composition buffer when
replying to messages.

After I went back to the default, my draft strangeness went away.
Editing a draft multiple times still creates multiple editing buffers
for that message, but maybe that's normal.

It also cleared up another, equally weird problem: my mairix search
results folder was appearing in random places in the filesystem. My org
directory, recent directories I'd been working in, other places gnus had
no business knowing about… My eventual sense was that my last 'pwd'
location before switching to gnus was somehow hanging around and getting
substituted for gnus' base directory. This is mostly useless as a bug
report, I know, but I can't help mentioning it.

It's all very magical, but that's why I love emacs/gnus…

Eric



      parent reply	other threads:[~2011-05-18 11:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-05  4:02 Eric Abrahamsen
2011-04-05 10:48 ` Richard Riley
2011-04-06  0:24 ` Lars Magne Ingebrigtsen
2011-04-06  1:43   ` Eric Abrahamsen
2011-04-06 13:28     ` quoting code blocks in Gnus without Org functions (was: draft group weirdness) Ted Zlatanov
2011-04-06 14:14       ` quoting code blocks in Gnus without Org functions Julien Danjou
2011-04-06 14:21         ` Ted Zlatanov
2011-04-06 14:45           ` Julien Danjou
2011-04-06 16:24             ` Ted Zlatanov
2011-04-07  7:38               ` Julien Danjou
2011-04-07 19:57                 ` Ted Zlatanov
2011-04-07 21:20                   ` Ted Zlatanov
2011-04-08  5:52                     ` Ted Zlatanov
2011-04-08  9:34                       ` Balázs Tóth
2011-04-08  9:40                   ` Julien Danjou
2011-04-11 18:47                     ` Ted Zlatanov
2011-04-10 15:50     ` draft group weirdness Eric Abrahamsen
2011-04-11 18:39       ` Ted Zlatanov
2011-04-10 15:54     ` Eric Abrahamsen
2011-04-12 16:21       ` Lars Magne Ingebrigtsen
2011-04-12 23:02         ` Eric Abrahamsen
2011-04-12 16:19     ` Lars Magne Ingebrigtsen
2011-05-18 11:39     ` Eric Abrahamsen [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=87ipt8dyqi.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).