Gnus development mailing list
 help / color / mirror / Atom feed
From: Emanuel Berg <moasenwood@zoho.eu>
To: ding@gnus.org
Subject: Re: *Group* inherits default-directory
Date: Thu, 07 Apr 2022 01:05:12 +0200	[thread overview]
Message-ID: <878rsh3j9z.fsf@zoho.eu> (raw)
In-Reply-To: <lzr1696cu8.fsf@3c22fb11fdab.ant.amazon.com>

Sam Steingold wrote:

> 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.

Sounds bad, does this only happens with Tramp tho?

It seems so, right?

To me it has always been

  /home/incal/News/

and I can guarantee you I don't muck around with that
directory nearly enough so that Gnus would be called from
there that often ...

And if it is "Tramp only" thing, maybe it makes sense in the
context of Tramp? Dunno, but anyway I'll try to call it from
a Tramp'd buffer myself in an instant to see if I can
replicate it (and I suspect I can) ...

-- 
underground experts united
https://dataswamp.org/~incal



  reply	other threads:[~2022-04-06 23:05 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 [this message]
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

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=878rsh3j9z.fsf@zoho.eu \
    --to=moasenwood@zoho.eu \
    --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).