From: Michael Albinus <michael.albinus@gmx.de>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: Tom Tromey <tom@tromey.com>, Noam Postavsky <npostavs@gmail.com>,
31495@debbugs.gnu.org
Subject: bug#31495: 26.1; filename completion -vs- "*"
Date: Thu, 21 Jun 2018 09:19:17 +0200 [thread overview]
Message-ID: <8736xg1ua2.fsf@gmx.de> (raw)
In-Reply-To: <87lgb87vs5.fsf@calancha-pc.dy.bbexcite.jp> (Tino Calancha's message of "Thu, 21 Jun 2018 10:50:18 +0900")
Tino Calancha <tino.calancha@gmail.com> writes:
Hi Tino,
this discussion is going offtopic. Maybe you write a bug report?
> I find-grep 'zsh' in doc, and I found from tramp manual just this:
> When using zsh on remote hosts, disable zsh line editor because zsh
> uses left-hand side and right-hand side prompts in parallel. Add the
> following line to @file{~/.zshrc}:
>
> @example
> [[ $TERM == "dumb" ]] && unsetopt zle && PS1='$ ' && return
> @end example
>
> Then, I add such line in
> ~/.zsh
> and
> /root/.zsh
> sudo ln -sf /bin/zsh /bin/sh
> emacs -Q
> C-x d /sudo::/bin
> ;; I don't get prompt for root password
Please eval (setq tramp-verbose 10) prior opening your remote
directory. There will be a Tramp debug buffer; pls show it.
Out of curiosity, why do you edit ~/.zsh and /root/.zsh? The manual
speaks about ~/.zshrc (I'm not an zsh user, so I don't know what I'm
speaking about).
Best regards, Michael.
next prev parent reply other threads:[~2018-06-21 7:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 15:33 bug#31495: 26.1; filename completion -vs- "*" Tom Tromey
2018-05-19 13:32 ` Tino Calancha
2018-05-19 18:17 ` Michael Albinus
2018-05-20 2:19 ` Tino Calancha
2018-06-20 12:36 ` Noam Postavsky
2018-06-20 12:48 ` Tino Calancha
2018-06-20 13:08 ` Tino Calancha
2018-06-20 14:05 ` Michael Albinus
2018-06-21 1:50 ` Tino Calancha
2018-06-21 7:19 ` Michael Albinus [this message]
2018-06-21 7:44 ` Tino Calancha
2020-08-22 15:40 ` Lars Ingebrigtsen
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=8736xg1ua2.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=31495@debbugs.gnu.org \
--cc=npostavs@gmail.com \
--cc=tino.calancha@gmail.com \
--cc=tom@tromey.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).