From: Uwe Brauer <oub@mat.ucm.es>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21565@debbugs.gnu.org, Uwe Brauer <oub@mat.ucm.es>
Subject: bug#21565: 25.0.50; ediff-regions-wordwise fails on latex files
Date: Sat, 26 Sep 2015 11:02:37 +0200 [thread overview]
Message-ID: <877fndr1si.fsf@mat.ucm.es> (raw)
In-Reply-To: <87r3lm700d.fsf@mat.ucm.es>
> I cannot reproduce this in "emacs -Q" with today's Git master. Does
> this happen to you in "emacs -Q" with any 2 buffers, not necessarily
> in AUC TeX mode? Or is AUC TeX a necessary part of this problem? (I
> tried 2 buffers in C Mode.)
I did not try emacs -Q, because then it is difficult for me to send the
bug report, since the smtp server is configured. I also use
ediff-region-wordwise either in mail or in Latex(auctex) buffers.
> Also, you seem to have a private jit-lock package:
> /home/oub/emacs/jit-lock hides /opt/emacs25/share/emacs/25.0.50/lisp/jit-lock
I deleted it
> which perhaps could be part of this problem.
> In general, the error seems to indicate one of the regions was absent
> (so no mark in that buffer), so presenting a detailed sequence of
> commands and keystrokes leading to the problem might also shed some
> light on this. (Reporting the bug immediately after it happened and
> from the same Emacs session would have captured your last keystrokes
> and included them in the report.)
Ok I did this, starting emacs -Q and working in a latex buffer (in that
case auctex is not used but the plain latex mode emacs still ships)
I therefore send another bug report and you might close this one, thanks.
next prev parent reply other threads:[~2015-09-26 9:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 19:49 bug#21565: 25.0.50; ediff-regions-wordwise fails on latex files Uwe Brauer
2015-09-26 7:52 ` Eli Zaretskii
2015-09-26 9:02 ` Uwe Brauer [this message]
2015-09-26 9:32 ` Eli Zaretskii
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=877fndr1si.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=21565@debbugs.gnu.org \
--cc=eliz@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 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.