unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jim Porter <jporterbugs@gmail.com>
To: Dmitry Gutov <dmitry@gutov.dev>,
	Michael Albinus <michael.albinus@gmx.de>,
	Eli Zaretskii <eliz@gnu.org>
Cc: Sean Allred <allred.sean@gmail.com>, 73320@debbugs.gnu.org
Subject: bug#73320: [PATCH] project--vc-list-files: use Git's sparse-index
Date: Sun, 6 Oct 2024 17:41:11 -0700	[thread overview]
Message-ID: <6c852997-44f6-4a84-f03c-2afd1c5704df@gmail.com> (raw)
In-Reply-To: <dbee6584-96a6-4225-9d92-a52465df8ac6@gutov.dev>

On 10/4/2024 2:25 PM, Dmitry Gutov wrote:
> Hi Michael, Eli,
> 
> On 04/10/2024 10:48, Michael Albinus wrote:
> 
>>> It could use some review, though. There aren't many examples of doing
>>> that in Emacs code.
>> In Eshell, Jim Porter makes extensive use of connection-local
>> variables. He has also added some functions which are useful (not
>> applied in Tramp yet).
> 
> Yep, Eshell seems to be have been the only other client of 
> connection-local, until now. I was wondering whether setting a unique 
> application name is the recommended pattern, though.

If I remember things correctly, I think using ":application eshell" was 
a suggestion from Michael Albinus. (I don't think I'd have come up with 
the idea on my own, since I didn't know much about connection-local 
variables at the time.)

However, I think can be a good move to use a unique application name 
when it makes sense because it reduces the chance of conflicts. For 
example, in a future version of Eshell, I might make 
'process-environment' connection-local for ":application eshell" (it's a 
long story). This would let users change remote env vars in Eshell 
freely without interfering with the ":application tramp" remote env 
vars, which would get used in other cases (e.g. when opening a remote 
file or using M-x shell remotely).





  parent reply	other threads:[~2024-10-07  0:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-17 16:55 bug#73320: [PATCH] project--vc-list-files: use Git's sparse-index Sean Allred
2024-09-17 22:54 ` Dmitry Gutov
2024-09-18  0:36   ` Sean Allred
2024-09-18 22:27     ` Dmitry Gutov
2024-09-19  4:25       ` Sean Allred
2024-09-19  9:44         ` Dmitry Gutov
2024-09-29  1:19           ` Dmitry Gutov
2024-10-03 23:57         ` Dmitry Gutov
2024-10-04  7:48           ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-04 21:25             ` Dmitry Gutov
2024-10-05  6:48               ` Eli Zaretskii
2024-10-05 12:33                 ` Dmitry Gutov
2024-10-07 23:55                   ` Dmitry Gutov
2024-10-07  0:41               ` Jim Porter [this message]
2024-10-07 23:38                 ` Dmitry Gutov
2024-09-19  5:41       ` Eli Zaretskii
2024-09-19  9:34         ` Dmitry Gutov

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6c852997-44f6-4a84-f03c-2afd1c5704df@gmail.com \
    --to=jporterbugs@gmail.com \
    --cc=73320@debbugs.gnu.org \
    --cc=allred.sean@gmail.com \
    --cc=dmitry@gutov.dev \
    --cc=eliz@gnu.org \
    --cc=michael.albinus@gmx.de \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).