From: Ivan Andrus <darthandrus@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 9324@debbugs.gnu.org, antoine.levitt@gmail.com
Subject: bug#9324: 24.0.50; Movement past end of screen causes weird jump
Date: Fri, 19 Aug 2011 20:38:09 +0200 [thread overview]
Message-ID: <9ACB0EEF-FA00-4644-9D76-727BFDD9CECF@gmail.com> (raw)
In-Reply-To: <83ty9dqq54.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1587 bytes --]
On Aug 19, 2011, at 7:15 PM, Eli Zaretskii wrote:
>> From: Ivan Andrus <darthandrus@gmail.com>
>> Date: Fri, 19 Aug 2011 18:19:47 +0200
>> Cc: antoine.levitt@gmail.com,
>> 9324@debbugs.gnu.org
>>
>> In case you are interested in what happens in my contaminated emacs, if I run C-x = after (forward-sexp) then it says a left parenthesis, but if I use `(progn (forward-sexp)(what-cursor-position))` then it says the next character is C-j. Furthermore, changing it to (prog2 (forward-sexp) (what-cursor-position) (redisplay)) causes it to work properly (i.e. no bug).
>
> If invoking `redisplay' fixes the problem, it means some display
> optimization is misfiring. But there are quite a few of those
> optimizations, so without a reproducible test case, it's really hard
> to say where to look.
>
>> I guess I'm probably on my own on this one, since even I can't reproduce it reliably in emacs -Q, so what functions that I should start debugging?
>
> I agree with Antoine: if you can reliably reproduce this with your
> ~/..emacs, bisect it to find the minimal customizations necessary to
> reproduce the problem, then post that information here.
Okay, I think I can reliably reproduce it now. Sorry it took so long to get it right. Anyway it seems to require both highlight-parentheses-mode and hl-sexp-mode as well as a custom mode-line face. I invoke it with:
emacs -Q -l ~/.emacs.d/elpa/highlight-parentheses-1.0.1/highlight-parentheses.el -l ~/.emacs.d/local/hl-sexp.el ~/vcs/emacs/bug-example-3.el
Thanks for your patience and pointers,
Ivan
[-- Attachment #2: bug-example-3.el --]
[-- Type: application/octet-stream, Size: 2418 bytes --]
208. look at docs for `mouse-autoselect-window' to see if there is a better value that I should be using
209. Look at occur (C-h f occur RET) to see how to make a nice menu buffer, thing-amagig
210. make isearch ignore diactritics by default (until one is used or something)
211. use `declare-function' to silence warnings in init.el
212. Change all key bindings to C-c C-f for compiling/linting/syntax checking, C-c C-d for debugging, and C-c C-v for viewing/running
213. Make `to-do' update an org file which contains all the todos
214. Make a `find-nearby' to find 2 things within several lines
215. Make `zap-up-to-char-but-not-including' a la `zap-to-char' (maybe on S-M-z ?)
216. Use `align-regexp' with args to create `align-words' and `align-strings'
-------------------------------------------------------
(custom-set-faces '(mode-line ((t (:box (:line-width 1))))))
(progn (set-frame-parameter (selected-frame) 'height 47)
(set-frame-parameter (selected-frame) 'width (/ 178 2))
;; (delete-other-windows)
;; (split-window-side-by-side)
(goto-line 22)
(recenter -22)
(move-end-of-line 1)
(emacs-lisp-mode) (highlight-parentheses-mode 1) (hl-sexp-mode 1)
)
(forward-sexp)
(defadvice server-goto-line-column (after server-visit-region.tex
(line-col)
activate)
"When visiting a file from an external source, make sure that we
are not narrowed, since the external source almost certainly
uses absolute file line numbers."
(when (string-match "_region_.tex\\'" (buffer-file-name))
(save-excursion ;; in case we don't find the other file we at least want the right line...
(if (re-search-backward
"\message{ !name(\\([^)]+\\))\\(?: !offset(\\([-0-9]+\\))\\)?\\s *}" nil nil)
(let ((file-name (match-string 1))
(offset (match-string 2))
(line (car (ad-get-arg 0)))
(col (cdr (ad-get-arg 0))))
(if offset (setq line (+ line (string-to-number offset))))
(find-file file-name nil)
;; Ironic, but I think cleaner then reimplementing...
(server-goto-line-column (cons line col))
(message "Moved from _region_.tex to line %s of %s." line file-name))
;; else
(message "This is _region_.tex, but I couldn't find the original file!")))))
next prev parent reply other threads:[~2011-08-19 18:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-18 20:48 bug#9324: 24.0.50; Movement past end of screen causes weird jump Ivan Andrus
2011-08-18 21:11 ` Antoine Levitt
2011-08-19 8:25 ` Eli Zaretskii
2011-08-19 9:54 ` Ivan Andrus
2011-08-19 10:02 ` Ivan Andrus
2011-08-19 10:41 ` Eli Zaretskii
2011-08-19 16:19 ` Ivan Andrus
2011-08-19 16:51 ` Antoine Levitt
2011-08-19 17:15 ` Eli Zaretskii
2011-08-19 18:38 ` Ivan Andrus [this message]
2011-08-19 19:06 ` Eli Zaretskii
2011-08-20 7:33 ` Ivan Andrus
2011-08-20 11:29 ` Eli Zaretskii
[not found] ` <0760243C-31D8-492E-99BE-86D87D7601F6@gmail.com>
2011-08-20 14:37 ` Eli Zaretskii
2011-08-25 20:11 ` Ivan Andrus
2011-08-25 20:59 ` Antoine Levitt
2011-08-26 10:32 ` Eli Zaretskii
2011-08-26 10:20 ` 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
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=9ACB0EEF-FA00-4644-9D76-727BFDD9CECF@gmail.com \
--to=darthandrus@gmail.com \
--cc=9324@debbugs.gnu.org \
--cc=antoine.levitt@gmail.com \
--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 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).