From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Markus Triska Newsgroups: gmane.emacs.bugs Subject: bug#23871: 25.1.50; Undo unexpectedly leads to blank buffer Date: Sat, 02 Jul 2016 07:35:31 +0200 Message-ID: <871t3cr49o.fsf@metalevel.at> References: <83h9cavdgj.fsf@gnu.org> <87poqyy2tc.fsf@metalevel.at> <87vb0qqrkz.fsf@russet.org.uk> <87h9c9zx75.fsf@metalevel.at> <834m89vmyv.fsf@gnu.org> <878txlsbdb.fsf@russet.org.uk> <87furtccdv.fsf@metalevel.at> <877fd5q9te.fsf@russet.org.uk> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1467437788 9248 80.91.229.3 (2 Jul 2016 05:36:28 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 2 Jul 2016 05:36:28 +0000 (UTC) Cc: 23871@debbugs.gnu.org To: phillip.lord@russet.org.uk (Phillip Lord) Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Jul 02 07:36:19 2016 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1bJDbE-0003Uh-OO for geb-bug-gnu-emacs@m.gmane.org; Sat, 02 Jul 2016 07:36:17 +0200 Original-Received: from localhost ([::1]:37006 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bJDbA-0001gt-36 for geb-bug-gnu-emacs@m.gmane.org; Sat, 02 Jul 2016 01:36:12 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:36345) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bJDb4-0001Zi-81 for bug-gnu-emacs@gnu.org; Sat, 02 Jul 2016 01:36:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bJDb0-0006uB-1u for bug-gnu-emacs@gnu.org; Sat, 02 Jul 2016 01:36:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:50205) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bJDaz-0006u7-Ut for bug-gnu-emacs@gnu.org; Sat, 02 Jul 2016 01:36:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1bJDaz-00034b-NN for bug-gnu-emacs@gnu.org; Sat, 02 Jul 2016 01:36:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Markus Triska Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 02 Jul 2016 05:36:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 23871 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 23871-submit@debbugs.gnu.org id=B23871.146743773611782 (code B ref 23871); Sat, 02 Jul 2016 05:36:01 +0000 Original-Received: (at 23871) by debbugs.gnu.org; 2 Jul 2016 05:35:36 +0000 Original-Received: from localhost ([127.0.0.1]:34309 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bJDaZ-00033y-Q3 for submit@debbugs.gnu.org; Sat, 02 Jul 2016 01:35:35 -0400 Original-Received: from metalevel.at ([78.46.218.83]:50302) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bJDaW-00033n-Jg for 23871@debbugs.gnu.org; Sat, 02 Jul 2016 01:35:33 -0400 Original-Received: by metalevel.at (Postfix, from userid 1000) id 74895A0339; Sat, 2 Jul 2016 07:35:31 +0200 (CEST) In-Reply-To: <877fd5q9te.fsf@russet.org.uk> (Phillip Lord's message of "Fri, 01 Jul 2016 23:21:01 +0100") User-Agent: Emacs/24.4 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:120275 Archived-At: phillip.lord@russet.org.uk (Phillip Lord) writes: > As an aside, probably would have been easier to include this in the > original message, rather than add a link. I only add a link if the spacing is critical, as in this case. Otherwise, I completely agree that in-line code is preferable. > I will investigate. Thank you for looking into this! All the best, Markus