[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Point of wrong window used in read-from-minibuffer?
From: |
Ulf Klaperski |
Subject: |
Point of wrong window used in read-from-minibuffer? |
Date: |
Mon, 4 Apr 2005 23:51:58 +0200 |
User-agent: |
Mutt/1.5.4i |
Hello!
Your bug report will be posted to the address@hidden mailing list.
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
- Load a vhdl file
- Divide emacs into two windows vertically, both showing the same buffer
- Jump to the end of the buffer in the upper window
- Switch to the lower window, near the beginning
- Type "signal " (with a space afterwards), this triggers the template insertion
mechanism for a signal
- type any name at the minibuffer prompt, eg. test and press return.
- type any type at the minibuffer prompt, eg. std_logic and press return.
-> ! The region between the signal and the point in the other buffer is
deleted !
- type any initialization value at the minibuffer prompt and press return.
-> Error message: "byte-code: Invalid search bound (wrong side of point)"
The problem is triggered in vhdl-template-field, it seems that
read-from-minibuffer switches to the point position of the wrong window.
I just did a "cvs update".
In previous emacs versions (some weeks older), the bug was already triggered
after the first minibuffer input.
I tried this with a 21.3 emacs without an error.
If you need an example vhdl file, I can send one to you.
Thanks,
Ulf
In GNU Emacs 22.0.50.1 (i686-pc-linux-gnu, GTK+ Version 2.2.4)
of 2005-04-04 on mordor
Distributor `The XFree86 Project, Inc', version 11.0.40300001
configured using `configure '--with-gtk' 'CFLAGS=-O3''
Important settings:
value of $LC_ALL: nil
value of $LC_COLLATE: nil
value of $LC_CTYPE: nil
value of $LC_MESSAGES: nil
value of $LC_MONETARY: nil
value of $LC_NUMERIC: nil
value of $LC_TIME: nil
value of $LANG: nil
locale-coding-system: nil
default-enable-multibyte-characters: t
Major mode: VHDL/es
Minor modes in effect:
auto-compression-mode: t
delete-selection-mode: t
display-time-mode: t
global-auto-revert-mode: t
recentf-mode: t
show-paren-mode: t
tooltip-mode: t
mouse-wheel-mode: t
menu-bar-mode: t
global-font-lock-mode: t
font-lock-mode: t
unify-8859-on-encoding-mode: t
utf-translate-cjk-mode: t
column-number-mode: t
line-number-mode: t
transient-mark-mode: t
next-error-follow-minor-mode: Fol
Recent input:
<help-echo> C-x C-f c h <return> C-x 5 C-g C-x 2 <escape>
> C-x o <next> <next> <down> <down> <down> <down> <down>
<down> <down> <down> <down> s i g n a l SPC t e s t
<return> s t d _ l o g i c <return> 0 <return> <help-echo>
<help-echo> <help-echo> <help-echo> <help-echo> <help-echo>
<help-echo> <help-echo> <help-echo> <help-echo> <help-echo>
<help-echo> <help-echo> <help-echo> <help-echo> <help-echo>
<help-echo> <help-echo> <help-echo> <help-echo> <help-echo>
<help-echo> <help-echo> <help-echo> <help-echo> <help-echo>
<help-echo> <menu-bar> <help-menu> <report-emacs-b
ug>
Recent messages:
Loading br-start...done
Loading jit-lock...done
Loading vhdl-mode...done
VHDL Mode 3.32.12. See menu for documentation and release notes.
Loading lazy-lock...done
Fontifying chip-minimal-a.vhd... (regexps..........................)
Loading lazy-lock...done
Mark set
byte-code: Invalid search bound (wrong side of point)
Loading emacsbug...done
--
Jabber-ID: address@hidden
- Point of wrong window used in read-from-minibuffer?,
Ulf Klaperski <=
- Re: Point of wrong window used in read-from-minibuffer?, Stefan Monnier, 2005/04/04
- Re: Point of wrong window used in read-from-minibuffer?, Stefan Monnier, 2005/04/05
- Re: Point of wrong window used in read-from-minibuffer?, Richard Stallman, 2005/04/13
- Re: Point of wrong window used in read-from-minibuffer?, Stefan Monnier, 2005/04/13
- Re: Point of wrong window used in read-from-minibuffer?, Richard Stallman, 2005/04/14