From: Michael Albinus <michael.albinus@gmx.de>
To: Max Brieiev <max.brieiev@gmail.com>
Cc: 49596-done@debbugs.gnu.org
Subject: bug#49596: 28.0.50; shadowfile.el: `shadow-define-literal-group' is broken
Date: Thu, 09 Sep 2021 15:55:38 +0200 [thread overview]
Message-ID: <877dfpua3p.fsf@gmx.de> (raw)
In-Reply-To: <875yvsbgoi.fsf@gmx.de> (Michael Albinus's message of "Thu, 26 Aug 2021 13:15:25 +0200")
Version: 28.1
Michael Albinus <michael.albinus@gmx.de> writes:
Hi Max,
>> Yes, the issue is fixed.
>
> Thanks for the feedback.
>
>> 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?
>
> Fixed.
>
>> - 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.
>
> I've adapted this. It prompts now for "Site name: ", and it has also a
> help echo describing what a site name is (move the mouse over the prompt).
> The error is fixed.
>
>> 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.
>
> That's an alternative. But the interactive command shall also work as
> expected.
No further comment, so I'm closing the bug. Feel free to report further
problems if available.
Best regards, Michael.
prev parent reply other threads:[~2021-09-09 13:55 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
2021-08-26 11:15 ` Michael Albinus
2021-09-09 13:55 ` Michael Albinus [this message]
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=877dfpua3p.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=49596-done@debbugs.gnu.org \
--cc=max.brieiev@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.