From: Michael Albinus via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eshel Yaron <me@eshelyaron.com>
Cc: Aaron Gonzales <aarongonzales1@gmail.com>,
59797@debbugs.gnu.org, Filipp Gunbin <fgunbin@fastmail.fm>,
Warren Lynn <wrn.lynn@gmail.com>
Subject: bug#59797: 30.0.50; [wishlist] Using namespaces in Tramp's kubernetes integration
Date: Tue, 23 Jul 2024 16:13:10 +0200 [thread overview]
Message-ID: <87plr4nqmh.fsf@gmx.de> (raw)
In-Reply-To: <m15xsw6z7b.fsf@eshelyaron.com> (Eshel Yaron's message of "Tue, 23 Jul 2024 14:59:52 +0200")
Eshel Yaron <me@eshelyaron.com> writes:
Hi Eshel,
>> Possible. However, the syntax is ambiguous. If we have "/kubernetes:name1.name2:/..."
>> it isn't clear what they are. name1 could be a container, and name2 a pod. Or
>> name1 is a pod, and name2 is a namespace. Could we agree on another
>> delimiter between POD and NAMESPACE?
>
> You're absolutely right. AFAIU from the Kubernetes documentation[0],
> non-alphanumeric characters other than "-" and "." should be safe.
> Maybe "@" would be the most natural choice? "+" could work too I think.
"@" is already used for the "user@host" notation in Tramp. We shouldn't
confuse users with another meaning in parallel. "+" might be OK, let's
start with it. It will be a Lisp constant, we can change it any time
later. So we have "/kubernetes:[CONTAINER.]POD[+NAMESPACE]:/..." now.
(If somebody has another proposal: it's time to stand up)
> Thank you!
Best regards, Michael.
next prev parent reply other threads:[~2024-07-23 14:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-03 9:20 bug#59797: 30.0.50; [wishlist] Using namespaces in Tramp's kubernetes integration Michael Albinus
2022-12-05 14:05 ` Filipp Gunbin
2022-12-05 15:54 ` Michael Albinus
2022-12-06 13:56 ` Filipp Gunbin
2022-12-06 15:13 ` Michael Albinus
2023-06-23 19:47 ` Michael Albinus
2023-07-02 8:37 ` Michael Albinus
[not found] ` <m1cyn4cq38.fsf@eshelyaron.com>
2024-07-23 12:29 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-23 12:59 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-23 14:13 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-07-24 16:48 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-24 17:30 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-25 8:20 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-25 10:48 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-25 11:42 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87plr4nqmh.fsf@gmx.de \
--to=bug-gnu-emacs@gnu.org \
--cc=59797@debbugs.gnu.org \
--cc=aarongonzales1@gmail.com \
--cc=fgunbin@fastmail.fm \
--cc=me@eshelyaron.com \
--cc=michael.albinus@gmx.de \
--cc=wrn.lynn@gmail.com \
/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).