Gnus development mailing list
 help / color / mirror / Atom feed
From: Sam Steingold <sds@gnu.org>
To: ding@gnus.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: Re: *Group* inherits default-directory
Date: Thu, 07 Apr 2022 11:21:04 -0400	[thread overview]
Message-ID: <lzmtgw6hsv.fsf@3c22fb11fdab.ant.amazon.com> (raw)
In-Reply-To: <878rshdcqa.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 07 Apr 2022 01:16:29 +0200")

> * Lars Ingebrigtsen <ynefv@tahf.bet> [2022-04-07 01:16:29 +0200]:
>
> Sam Steingold <sds@gnu.org> writes:
>
>> I encountered a pretty bad interaction between Gnus and Tramp
>> (see
>> https://lists.gnu.org/archive/html/tramp-devel/2022-04/msg00003.html
>> and ff)
>> because the `*Group*` buffer inherits `default-directory' from the
>> buffer from which Gnus is called.
>
> This is how most special mode buffers work -- they inherit the
> `default-directory' from when they were started.

yeah, and it _is_ a problem for me in this case.

> If you want something else in Gnus, set `gnus-default-directory'.

oops, I have always been setting this - how come it failed to work?!
okay, I will try to debug this...

thanks.

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.2113
http://childpsy.net http://calmchildstories.com http://steingoldpsychology.com
https://jij.org https://thereligionofpeace.com https://ffii.org https://ij.org/
When we break the law, they fine us, when we comply, they tax us.


      parent reply	other threads:[~2022-04-07 15:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 22:55 Sam Steingold
2022-04-06 23:05 ` Emanuel Berg
2022-04-06 23:10   ` Emanuel Berg
2022-04-06 23:16 ` Lars Ingebrigtsen
2022-04-06 23:20   ` Emanuel Berg
2022-04-07  7:10     ` Michael Albinus
2022-04-12  2:04       ` Emanuel Berg
2022-04-12  8:07         ` Michael Albinus
2022-04-13  2:46           ` Emanuel Berg
2022-04-13  3:06             ` Emanuel Berg
2022-04-07 15:21   ` Sam Steingold [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=lzmtgw6hsv.fsf@3c22fb11fdab.ant.amazon.com \
    --to=sds@gnu.org \
    --cc=ding@gnus.org \
    --cc=larsi@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).