From: Lars Ingebrigtsen <larsi@gnus.org>
To: richard_sharman@mitel.com
Cc: 4784@debbugs.gnu.org
Subject: bug#4784: variable telnet-remote-echoes non-nil causes comint-previous-prompt to fail
Date: Thu, 21 Jan 2021 17:28:09 +0100 [thread overview]
Message-ID: <87v9bq6yqu.fsf@gnus.org> (raw)
In-Reply-To: <200910221436.n9MEaBMX031160@sharmanpc.mitel.com> (richard sharman's message of "Thu, 22 Oct 2009 10:36:11 -0400")
richard_sharman@mitel.com writes:
> When running the telnet command, if variable telnet-remote-echoes is
> set, then the command comint-previous-prompt deletes the field text
> property that the command comint-previous-prompt uses (assuming that
> variable comint-use-prompt-regexp is nil). It also removes the
> mouse-highlighting and so mouse-2 cannot be used to re-insert that
> command.
>
> There is no need for variable telnet-remote-echoes because variable
> comint-process-echoes can be used to remove the second copy, and it does
> it without removing the text properties.
(I'm going through old bug reports that unfortunately got no response at
the time.)
I tried `M-x telnet' with `telnet-remote-echoes' set (and the other
variables also have the values described), and everything looks normal
to me.
I'm not sure what problem this bug report describes -- I have no mouse
highlight in the *telnet* buffer, and I'm not sure what that has to do
with do with `C-c C-p' (`comint-previous-point').
This is with Emacs 28, though, so perhaps what's being described here
has been fixed in the 11 years since this was reported.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-01-21 16:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 14:36 bug#4784: variable telnet-remote-echoes non-nil causes comint-previous-prompt to fail richard_sharman
2021-01-21 16:28 ` Lars Ingebrigtsen [this message]
2021-02-22 15:15 ` 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=87v9bq6yqu.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=4784@debbugs.gnu.org \
--cc=richard_sharman@mitel.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).