From: Max Brieiev <max.brieiev@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 49596@debbugs.gnu.org
Subject: bug#49596: 28.0.50; shadowfile.el: `shadow-define-literal-group' is broken
Date: Fri, 20 Aug 2021 16:45:02 +0300 [thread overview]
Message-ID: <874kbkw7q9.fsf@gmail.com> (raw)
In-Reply-To: <87k0l6r3jl.fsf@gmx.de> (Michael Albinus's message of "Sat, 31 Jul 2021 15:55:26 +0200")
Hi Michael,
Sorry for being quiet for a long time.
Yes, the issue is fixed.
However, the interface of `shadow-define-literal-group` is somewhat
obscure:
- `M-x shadow-define-literal-group RET RET` will insert `nil` into
`shadow-literal-groups`, which is probably not correct?
- The first prompt `Host identification or cluster name: ` isn't very
descriptive. There is not much docs and I had to learn by trial and
error that it accepts either tramp format like `/ssh:user@host:` for
remote endpoints or a plain string like `my-linux-box` for local host
names. And it seems if it can't resolve provided host name it will
silently insert `nil` into `shadow-literal-groups`, which also doesn't
seem correct.
That said, it is easier to set `shadow-literal-groups` manually, because
you can manually test accessibility of remote files and then simply
append the resulting tramp file name into the variable.
next prev parent reply other threads:[~2021-08-20 13:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 13:49 bug#49596: 28.0.50; shadowfile.el: `shadow-define-literal-group' is broken Max Brieiev
2021-07-17 12:37 ` Michael Albinus
2021-07-18 14:01 ` Michael Albinus
2021-07-19 15:34 ` Max Brieiev
2021-07-20 17:24 ` Michael Albinus
2021-07-31 13:55 ` Michael Albinus
2021-08-20 13:45 ` Max Brieiev [this message]
2021-08-26 11:15 ` Michael Albinus
2021-09-09 13:55 ` 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=874kbkw7q9.fsf@gmail.com \
--to=max.brieiev@gmail.com \
--cc=49596@debbugs.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).