unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Reuben Thomas via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 7041@debbugs.gnu.org
Subject: bug#7041: comint seems to truncate from places other than the top
Date: Tue, 8 Dec 2020 22:37:52 +0000	[thread overview]
Message-ID: <CAOnWdoiQF8enshqXgCCd5xvg6Gt8F5bdMQe=u_AZnacDsKNL3Q@mail.gmail.com> (raw)
In-Reply-To: <87lfe87ww9.fsf@gnus.org>

[-- Attachment #1: Type: text/plain, Size: 1543 bytes --]

On Tue, 8 Dec 2020 at 22:31, Lars Ingebrigtsen <larsi@gnus.org> wrote:

> Reuben Thomas <rrt@sc3d.org> writes:
>
> > If I try it now, it doesn't seem to truncate the buffer as expected: for
> example
> >
> > emacs -Q
> > M-: (add-to-list 'comint-output-filter-functions 'comint-truncate-buffer)
> > M-x term
> > C-c M-x set-variable comint-buffer-maximum-size 256 ; do this after M-x
> term
> > because before comint-buffer-maximum-size is not defined
> > $ seq 1 1024
> >
> > The entire output is retained, and not truncated. Truncation seems to
> happen at
> > 2048 lines. This does not even correspond to the original value of the
> variable
> > (1024).
>
> I'm not getting any truncation...  but that variable is about comint
> buffers, like in `M-x shell' and the like.  Is term-mode a comint
> buffer?  It's not derived from comint-mode, so I'm not sure whether this
> is supposed to work there?
>

Ah, that would seem to explain it! Indeed, `term-buffer-maximum-size`
defaults to 2048.

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

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?

-- 
https://rrt.sc3d.org

[-- Attachment #2: Type: text/html, Size: 3215 bytes --]

  reply	other threads:[~2020-12-08 22:37 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 [this message]
2020-12-08 22:42         ` 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='CAOnWdoiQF8enshqXgCCd5xvg6Gt8F5bdMQe=u_AZnacDsKNL3Q@mail.gmail.com' \
    --to=bug-gnu-emacs@gnu.org \
    --cc=7041@debbugs.gnu.org \
    --cc=larsi@gnus.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 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).