Gnus development mailing list
 help / color / mirror / Atom feed
From: Paul Collins <paul@burly.ondioline.org>
To: ding@gnus.org
Subject: Re: advising gnus - a report from the front lines
Date: Sun, 25 May 2008 12:30:47 +1200	[thread overview]
Message-ID: <87skw7w7go.fsf@burly.wgtn.ondioline.org> (raw)
In-Reply-To: <87r6bscmem.fsf@grepfind.mwolson.org> (Michael Olson's message of "Fri, 23 May 2008 22:16:01 -0700")

Michael Olson <mwolson@member.fsf.org> writes:

> Paul Collins <paul@burly.ondioline.org> writes:
>
>> I recently added the following piece of advice:
>>
>>     (defadvice gnus (before gnus-homedir-advice activate)
>>        (cd (expand-file-name "~/")))
>>
>> This is so that subprocesses started by Gnus (e.g. my IMAP wossname)
>> don't end up with a network directory as their cwd. [snipped]
>
> Setting `gnus-default-directory' might help.

This does what I want, and it's also not terminally broken like I have
just realized the piece of advice above is.  Changing the cwd of random
buffers turns out to cause confusing behaviour.

Thanks also Daniel for your informative reply.

Regards,
-- 
Paul Collins
Wellington, New Zealand

Dag vijandelijk luchtschip de huismeester is dood



  reply	other threads:[~2008-05-25  0:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-22  8:37 Paul Collins
2008-05-24  5:16 ` Michael Olson
2008-05-25  0:30   ` Paul Collins [this message]
2008-05-24  6:27 ` Daniel Pittman

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=87skw7w7go.fsf@burly.wgtn.ondioline.org \
    --to=paul@burly.ondioline.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).