From: Thierry Volpiatto <thievol@posteo.net>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Madhu <enometh@meer.net>, emacs-devel@gnu.org
Subject: Re: tramp "too many open files" [Re: bug#56606
Date: Mon, 20 Mar 2023 16:57:56 +0000 [thread overview]
Message-ID: <87r0tjibia.fsf@posteo.net> (raw)
In-Reply-To: <87jzzbzbys.fsf@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]
Hi Michael,
Michael Albinus <michael.albinus@gmx.de> writes:
> Thierry Volpiatto <thievol@posteo.net> writes:
>
> Hi Thierry,
>
>> From the Helm help:
>>
>> As Tramp archive often crash Helm and Emacs, Helm does its best
>> to disable it, however it is hard to do so as Tramp Archive is
>> enabled inconditionally in Emacs. Here I build my Emacs
>> without-dbus to ensure Tramp archive wont kickin unexpectedly.
>
> There are two ways to disable tramp-archive.el:
>
> - Set or bind tramp-archive-enabled to nil.
I know but it is not enough in some cases. I think it should be up to
the user to set this, however it is already set and autoloaded in tramp-archive.el:
(defvar tramp-archive-enabled (featurep 'dbusbind)
"Non-nil when file archive support is available.")
> - Avoid file names like "/path/to/file.tar/". The combination of a known
> extension with a slash triggers tramp-archive.el. Usually, it is an
> error to specify such a file name, if not intended.
Agree, but we sometimes get files from elsewhere with such filenames, of
course I never name my files/dirs like this.
Anyway I think tramp-archive should not kick in with such filenames or
any filenames unless user wants it.
Thanks.
--
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 686 bytes --]
next prev parent reply other threads:[~2023-03-20 16:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86ilnwafso.fsf@stephe-leake.org>
[not found] ` <handler.56606.B.165800822832001.ack@debbugs.gnu.org>
[not found] ` <86a6989itv.fsf@stephe-leake.org>
[not found] ` <8335f0qbvn.fsf@gnu.org>
[not found] ` <831qujrjnm.fsf@gnu.org>
[not found] ` <86h73ex91m.fsf@stephe-leake.org>
[not found] ` <83k089omhb.fsf@gnu.org>
2023-03-20 13:31 ` tramp "too many open files" [Re: bug#56606 Madhu
2023-03-20 14:58 ` Thierry Volpiatto
2023-03-20 15:20 ` Michael Albinus
2023-03-20 16:57 ` Thierry Volpiatto [this message]
2023-03-20 17:56 ` Michael Albinus
2023-03-21 5:55 ` Thierry Volpiatto
2023-03-21 9:22 ` Michael Albinus
2023-03-21 13:43 ` Thierry Volpiatto
2023-03-21 15:17 ` Michael Albinus
2023-03-21 17:19 ` Thierry Volpiatto
2023-03-20 15:04 ` Michael Albinus
2023-03-20 18:47 ` Madhu
2023-03-21 9:30 ` Michael Albinus
2023-03-25 23:23 ` {Spam?} " Madhu
2023-03-26 18:56 ` tramp "too many open files" Michael Albinus
2023-05-14 5:44 ` Build failure: " Madhu
2023-05-14 7:10 ` Michael Albinus
2023-05-14 10:00 ` {Spam?} " Madhu
2023-05-14 11:24 ` Michael Albinus
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=87r0tjibia.fsf@posteo.net \
--to=thievol@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=enometh@meer.net \
--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).