From: kifer@cs.sunysb.edu (Michael Kifer)
To: andreas.amann@web.de
Cc: Chong Yidong <cyd@stupidchicken.com>, bug-gnu-emacs@gnu.org, rms@gnu.org
Subject: Re: [andreas.amann@web.de: ediff problem with longlines-show-hard-newlines]
Date: Mon, 09 Jul 2007 12:49:13 -0400 [thread overview]
Message-ID: <12238.1183999753@cs.sunysb.edu> (raw)
In-Reply-To: Message from Richard Stallman <rms@gnu.org> of "Fri, 06 Jul 2007 00:39:03 EDT." <E1I6fax-0006UI-FY@fencepost.gnu.org>
> Date: Thu, 5 Jul 2007 15:14:16 +0100
> From: Andreas Amann <andreas.amann@web.de>
> To: bug-gnu-emacs@gnu.org
> Subject: ediff problem with longlines-show-hard-newlines
>
>
> entering ediff-buffers and leaving it immediately sets the modified
> flags of the visited buffers, even if no editing was done. This only
> happens if longlines-show-hard-newlines is set to true.
>
>
> Minimal test case:
> >cat ~/.emacs
> (require 'longlines)
> (add-hook 'text-mode-hook (lambda () (longlines-mode 1)))
> (setq longlines-show-hard-newlines t)
>
> >cat testcase_ediff.txt
> A C
>
> >cat testcase_ediff2.txt
> A B C
>
> >emacs -no-site-file testcase_ediff.txt testcase_ediff2.txt
> "M-x ediff-buffers" and select the two loaded buffers
> "q" to quit ediff ("yes" to confirm)
>
> now the modified flags "**" are set for both buffers although no
> editing was done.
This is because with your settings:
(require 'longlines)
(add-hook 'text-mode-hook (lambda () (longlines-mode 1)))
(setq longlines-show-hard-newlines t)
executing (longlines-mode 0) marks text buffers as modified.
It seems to me a problem with longlines-mode rather than with ediff.
I am copying this to the maintainer of longlines.el for clarifications.
parent reply other threads:[~2007-07-09 16:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <E1I6fax-0006UI-FY@fencepost.gnu.org>]
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=12238.1183999753@cs.sunysb.edu \
--to=kifer@cs.sunysb.edu \
--cc=andreas.amann@web.de \
--cc=bug-gnu-emacs@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=rms@gnu.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).