unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Leo <sdl.web@gmail.com>
Cc: 6691@debbugs.gnu.org, John Wiegley <jwiegley@gmail.com>
Subject: bug#6691: 23.2; Eshell and ^M (PATCH attached)
Date: Wed, 11 Apr 2012 13:16:34 +0200	[thread overview]
Message-ID: <m3lim2wmb1.fsf@stories.gnus.org> (raw)
In-Reply-To: <m17hkn356r.fsf@cam.ac.uk> (Leo's message of "Thu, 22 Jul 2010 16:30:04 +0100")

Leo <sdl.web@gmail.com> writes:

> The problem is eshell-last-output-block-begin can point to a wrong
> position in the eshell buffer after truncating buffer. I tried to trace
> the reason of introducing eshell-last-output-block-begin but the
> revision history only goes back to 2000.

This looks like a good patch to me, but I don't use eshell, so I can't
test.

Does anybody know whether the `eshell-last-output-block-begin' stuff
really is cruft that can be removed?

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





  reply	other threads:[~2012-04-11 11:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-21 15:09 bug#6691: 23.2; Eshell and ^M Leo
2010-07-22 15:30 ` bug#6691: 23.2; Eshell and ^M (PATCH attached) Leo
2012-04-11 11:16   ` Lars Magne Ingebrigtsen [this message]
2012-04-12  0:40     ` John Wiegley
2012-04-12 12:27       ` Lars Magne Ingebrigtsen
2012-04-12 13:35         ` John Wiegley
2012-04-12  1:23 ` bug#6691: 23.2; Eshell and ^M Glenn Morris
2012-04-14  7:48   ` Leo
2012-04-14  8:22     ` Andreas Schwab
2012-04-14  8:58     ` Eli Zaretskii
2012-04-14  9:16     ` Andreas Schwab
2012-04-14  8:27 ` Andreas Schwab
2012-04-14  8:33   ` Leo
2012-04-14  8:53     ` Andreas Schwab
2012-04-16 12:19       ` Leo
2012-04-16 13:45         ` Andreas Schwab
2012-04-16 13:59           ` Leo
2013-06-13  6:50             ` Glenn Morris

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=m3lim2wmb1.fsf@stories.gnus.org \
    --to=larsi@gnus.org \
    --cc=6691@debbugs.gnu.org \
    --cc=jwiegley@gmail.com \
    --cc=sdl.web@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 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).