all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Reuben Thomas <rrt@sc3d.org>
Cc: 7041@debbugs.gnu.org
Subject: bug#7041: comint seems to truncate from places other than the top
Date: Tue, 08 Dec 2020 23:42:47 +0100	[thread overview]
Message-ID: <87blf39axk.fsf@gnus.org> (raw)
In-Reply-To: <CAOnWdoiQF8enshqXgCCd5xvg6Gt8F5bdMQe=u_AZnacDsKNL3Q@mail.gmail.com> (Reuben Thomas's message of "Tue, 8 Dec 2020 22:37:52 +0000")

Reuben Thomas <rrt@sc3d.org> writes:

> So this bug report is based on a misunderstanding, and you can close
> it, sorry!

No problem; I often get confused by which modes are comint modes and
which aren't myself.

> In investigating, I noticed that the following text in term.el appears to be out of
> date:
>
> ;; Brief Command Documentation:
> … for example:
> ;; M-s     comint-next-matching-input    Next input that matches ← This is not true!
> It is bound to term-next-matching-input.
>
> Is there any point retaining this documentation at the top of the file
> where it doesn't appear in the manual or any docstring?

Nope; I've now pushed a fix for this to Emacs 28.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2020-12-08 22:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-16 11:42 bug#7041: comint seems to truncate from places other than the top Reuben Thomas
2020-12-08 16:42 ` Lars Ingebrigtsen
2020-12-08 19:18   ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-08 22:31     ` Lars Ingebrigtsen
2020-12-08 22:37       ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-08 22:42         ` Lars Ingebrigtsen [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=87blf39axk.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=7041@debbugs.gnu.org \
    --cc=rrt@sc3d.org \
    /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.