From: Michael Olson <mwolson@member.fsf.org>
To: ding@gnus.org
Subject: Re: advising gnus - a report from the front lines
Date: Fri, 23 May 2008 22:16:01 -0700 [thread overview]
Message-ID: <87r6bscmem.fsf@grepfind.mwolson.org> (raw)
In-Reply-To: <87od6yhgyg.fsf@burly.wgtn.ondioline.org> (Paul Collins's message of "Thu, 22 May 2008 20:37:59 +1200")
[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]
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. However, advising
> the `gnus' function makes its check for compiled-ness trip, which is
> annoying since I habitually recall *Group* with `M-x gnus RET'. I've
> removed the check from my local copy, but it might be nice to fix it
> in Gnus so that it doesn't trip others up.
Setting `gnus-default-directory' might help. Maybe the
`gnus-set-default-directory' function could force the current directory
to be something sane if (file-remote-p default-directory) is non-nil.
--
| Michael Olson | FSF Associate Member #652 |
| http://mwolson.org/ | Hobbies: Lisp, HCoop |
| Projects: Emacs, Muse, ERC, EMMS, ErBot, DVC, Planner |
`-------------------------------------------------------'
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2008-05-24 5:16 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 [this message]
2008-05-25 0:30 ` Paul Collins
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=87r6bscmem.fsf@grepfind.mwolson.org \
--to=mwolson@member.fsf.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).