* Juri Linkov (2007-06-08) writes:
,[ http://mid.gmane.org/E1Dnaf1-0007am-Cg%40neutrino.iwi.uni-sb.de ]
| An open issue is the key binding for toggling the mode. If the minor
| mode should be able to be activated in some major modes but not in
| others, it doesn't make much sense to bind
* Leo (2007-06-07) writes:
I put (scroll-lock-mode t) in ~/.emacs, but it is still disabled after
restart emacs. Is this a bug in scroll-lock-mode?
Scroll Lock mode is a buffer-local minor mode, so your command will not
enable it globally. You can enable it via a hook. For example, if you
* Leo (2007-06-07) writes:
- Ralf Angeli (2007-06-07) wrote:-
* Leo (2007-06-07) writes:
I put (scroll-lock-mode t) in ~/.emacs, but it is still disabled after
restart emacs. Is this a bug in scroll-lock-mode?
Scroll Lock mode is a buffer-local minor mode, so your command
* Leo (2007-06-07) writes:
- Ralf Angeli (2007-06-07) wrote:-
Scroll Lock mode is a buffer-local minor mode, so your command will not
enable it globally. You can enable it via a hook. For example, if you
wanted the mode to be activated when browsing info files, you could do
* Juri Linkov (2007-06-07) writes:
I put (scroll-lock-mode t) in ~/.emacs, but it is still disabled after
restart emacs. Is this a bug in scroll-lock-mode?
Scroll Lock mode is a buffer-local minor mode, so your command will not
enable it globally. You can enable it via a hook. For example,
* Eivind Midtgård (2007-05-06) writes:
I wonder if the problem is in x_make_frame_visible in w32term.c,
because it explicitly assumes the taskbar is at the bottom.
/* Adjust vertical window position in order to avoid being
covered by a task bar placed at the bottom of the
* Chong Yidong (2007-03-03) writes:
Ralf Angeli [EMAIL PROTECTED] writes:
Trying to untar an Emacs pretest tar ball (22.0.94) with
`tar-untar-buffer' results in the following backtrace:
I checked in a fix for this.
I can confirm that it is working now. Thanks very much!
--
Ralf
Trying to untar an Emacs pretest tar ball (22.0.94) with
`tar-untar-buffer' results in the following backtrace:
Debugger entered--Lisp error: (error Invalid search bound (wrong side of
point))
re-search-forward([
\n]\\([^[
\n]*\\)[]*Local Variables:[ ]*\\([^
\n]*\\)[
\n] 342875 t)
* Jason Rumney (2007-02-23) writes:
Lennart Borgman (gmail) wrote:
Ah, then should not menu_kill_timer be called from within
w32_free_menu_strings (or always before that)?
I have fixed it now. I moved the freeing of strings earlier for popup
menus, so we can guarantee they are freed even
After doing an update of the sources from CVS today, `make bootstrap'
does not finish anymore. The last command in the terminal is
EMACSLOADPATH=/usr/src/emacs/leim/../lisp LC_ALL=C ../src/emacs -batch
--no-init -file --no-site-file --multibyte -f batch-byte-compile
quail/ZIRANMA.el
which
* Romain Francoise (2007-01-24) writes:
Ralf Angeli [EMAIL PROTECTED] writes:
After doing an update of the sources from CVS today, `make
bootstrap' does not finish anymore.
It does finish but it's *very* slow; compiling this file now takes
about 5 minutes on my computer where it took only
* Jason Rumney (2007-01-09) writes:
Prof. G. Venkatarathnam wrote:
The cursor is absent in my emacs in the beginning. If I delete a
character after marking it, I get the usual block cursor. How do I
make my cursor visible ? I din’t have this problem before. I’m using
the latest version
* Reiner Steib (2007-01-01) writes:
On Sun, Dec 31 2006, Ralf Angeli wrote:
With the setting
(setq mm-verify-option 'known)
the raw article will be shown for a split second before the rendered
one appears when an encrypted article like
[EMAIL PROTECTED] (from emacs-devel
With the setting
(setq mm-verify-option 'known)
the raw article will be shown for a split second before the rendered
one appears when an encrypted article like
[EMAIL PROTECTED] (from emacs-devel) is to be
displayed in Gnus (up-to-date No Gnus).
I tried to debug the problem but got stuck in
* Jason Rumney (2006-08-04) writes:
Ralf Angeli wrote:
IIUC the next step is to look at why get_menu_item_info puts an
integer into dwItemData.
It's a pointer.
Oh, I see.
I can't reproduce the problem,
For convenience reasons I am checking this by loading a LaTeX file and
opening
* Jason Rumney (2006-08-04) writes:
Ralf Angeli [EMAIL PROTECTED] writes:
Hm, a Google search regarding _libkernel32_a_iname revealed nothing
really interesting.
iname is used to denote an unknown function, in this case it is in
libkernel32 (I assume this is mingw's name for the system
* Ralf Angeli (2006-07-27) writes:
We received a bug report on the AUCTeX list about a crash of Emacs
under Windows. The report including a description on how to reproduce
the crash can be found at
URL:http://thread.gmane.org/gmane.emacs.auctex.general/1281/focus=1286.
Here is a backtrace I
* Eli Zaretskii (2006-08-03) writes:
Put a watchpoint to watch *(char *)0x85f988, and see what code
modifies it.
Thanks for the hint. That's what I get when playing around with it a
little bit (control characters replaced by strings again):
Breakpoint 1, w32_wnd_proc (hwnd=0x101f0, msg=43,
* Kim F. Storm (2006-07-21) writes:
Ralf Angeli [EMAIL PROTECTED] writes:
+ left = w32_get_arg (Qnil, Qleft, left, Left, RES_TYPE_NUMBER);
+ if (!EQ (left, Qunbound))
+CHECK_NUMBER (left);
One gripe I have with it is that the CHECK_NUMBER macro does not seem
to work. If I use
* Eli Zaretskii (2006-07-22) writes:
Thanks, I installed its modified version, given the discussions after
you posted the change.
Thanks!
One additional thought regarding CHECK_NUMER: x_get_arg returning 0
for an invalid value if RES_TYPE_NUMBER is used, might just be an
implementation
* Ralf Angeli (2006-07-20) writes:
* Drew Adams (2006-07-19) writes:
This problem occurs even for emacs -Q: the initial frame is about 5cm from
the left edge and about 6cm from the top edge of the display. Before, it was
flush with both top and left display edges.
Frame positioning is now
* Drew Adams (2006-07-19) writes:
This problem occurs even for emacs -Q: the initial frame is about 5cm from
the left edge and about 6cm from the top edge of the display. Before, it was
flush with both top and left display edges.
Frame positioning is now left to Windows unless you specified
* Eli Zaretskii (2006-06-23) writes:
One possible way of solving this would be to call SystemParametersInfo
with SPI_GETWORKAREA arg in x_make_frame_visible, and fix f-left_pos
and f-top_pos we pass to x_set_offset, if their values are inside the
task bar. I think this should be done for all
* Eli Zaretskii (2006-06-26) writes:
From: Ralf Angeli [EMAIL PROTECTED]
Frankly, I cannot answer this question with knowledge about how frame
placement works in Windows. There simply wasn't any problem when I
tried it.
Are you saying that, with the task bar on the left, the original
* Eli Zaretskii (2006-06-23) writes:
From: Ralf Angeli [EMAIL PROTECTED]
Date: Mon, 12 Jun 2006 23:25:46 +0200
It turned out that `x_set_offset' was called with `f-left_pos' and
`f-top_pos' as arguments which have to be updated after the frame was
created. The following patch works for me
* Eli Zaretskii (2006-06-23) writes:
Could you perhaps find time to try this approach?
I should be able to invest some time this weekend. I'll post the
outcome of this investment. Thanks for the hints.
--
Ralf
___
emacs-pretest-bug mailing list
* Eli Zaretskii (2006-06-12) writes:
From: Ralf Angeli [EMAIL PROTECTED]
I suspect that `x_set_offset' is called somewhere with values of 0
for both offsets
Correct.
but I could not find the respective call.
You could find that call with a debugger, by setting a breakpoint
* Stephan Hennig (2006-05-24) writes:
Emacs' frame appears in the top left corner of the screen. On Windows OS
this is ok when the OS's symbol panel (Symbolleiste) is located at the
bottom of the screen. If the symbol panel is located at the top of the
screen part of Emacs' frame -- the title
* Eli Zaretskii (2006-06-05) writes:
From: Drew Adams [EMAIL PROTECTED]
Date: Sun, 4 Jun 2006 17:34:00 -0700
I'm not certain it should be, as I'm not clear on how this user option
works.
I don't think it should be: it's not for users. It's for Lisp
programs that need special attention
* Kim F. Storm (2006-06-05) writes:
Eli Zaretskii [EMAIL PROTECTED] writes:
From: Ralf Angeli [EMAIL PROTECTED]
I have [redisplay-dont-pause] enabled for all my Emacs installations
because I cannot stand the way buffer contents are updated during
scrolling if it is not.
I think that's
(tex-font-lock-match-suscript): New
function.
(tex-font-lock-keywords-3): Use it.
Thanks, installed.
Thanks. Meanwhile I saw that there is a misplaced paren in the patch.
The following change should fix this. Sorry for the inconvenience.
2006-04-17 Ralf Angeli [EMAIL PROTECTED
* Richard Stallman (2006-04-10) writes:
emacs -Q -f toggle-debug-on-error test.c
the following error occurs:
Debugger entered--Lisp error: (void-variable c-subword-mode)
It did not happen for me on GNU/Linux.
(I fetched the sources today and rebuilt.)
I just
* Eli Zaretskii (2006-04-11) writes:
From: Ralf Angeli [EMAIL PROTECTED]
Date: Mon, 10 Apr 2006 23:07:00 +0200
Thanks, I'll do this as soon as I will have access to a better
connection again. (Or find out why cvs sends half of the repository
to the server during an update
* Eli Zaretskii (2006-04-11) writes:
From: Ralf Angeli [EMAIL PROTECTED]
Date: Mon, 10 Apr 2006 23:07:00 +0200
The question is, is this a bug or a feature? That is, is it right for
Emacs on MS-Windows to create Unix-style text files under LANG=C? I
tend to think it's a bug, but I'm
* Stefan Monnier (2006-04-11) writes:
now as soon as I'll find the time. At least cvs status tells me that
some sample files I've looked at are up-to-date.
`cvs status' checks the actual contents of the file (sending the local file
to the server, if needed), so it's not a good predictor for
* Eli Zaretskii (2006-04-10) writes:
From: Ralf Angeli [EMAIL PROTECTED]
Date: Sun, 09 Apr 2006 13:32:35 +0200
Trying to start Emacs from an MSYS shell with the command line
LANG=C drive:/path/to/emacs -Q
results in
Wrong type argument: arrayp, nil
Thanks, I think I fixed
The following bug report originally was sent to the AUCTeX bug list.
I can sort of reproduce this with a Windows build of 2006-03-09 in
Text mode, so this is rather an Emacs issue than one of AUCTeX. I am
writing sort of because I cannot reproduce it reliably. The yank
does not happen every time
* Eli Zaretskii (2006-04-08) writes:
From: Ralf Angeli [EMAIL PROTECTED]
I can sort of reproduce this with a Windows build of 2006-03-09
[...]
This bug, which was indeed specific to MS-Windows, was fixed on
2006-03-11
Argh, sooo close. (c:
--
Ralf
When starting Emacs with
emacs -Q -f toggle-debug-on-error test.c
the following error occurs:
Debugger entered--Lisp error: (void-variable c-subword-mode)
Ater quitting the debugger with `q' the error can be provoked as well
by clicking with the mouse on a menu. (That's in fact the way I
Under certain circumstances saving safe local variables permanently,
i.e. answering with `!' to the respective question may garble 8-bit
characters in a .emacs file. For this to happen the .emacs file has
to contain UTF-8 characters and has to be saved as UTF-8. In addition
Emacs has to be
Evaluating the following form will create two adjacent overlays and
point will be stuck at the top of the buffer (at least visually; there
still is feedback, e.g. beeping, if you hold `C-n' long enough and hit
the bottom of the buffer).
(progn
(pop-to-buffer (get-buffer-create *foo*))
(insert
* Chong Yidong (2006-02-19) writes:
The menu item Options -- Save Options does not work anymore. In
order to check this, change one of the values in the Options menu,
e.g. Blinking Cursor, click on the Save Options menu item and
compare your init file with a backup you did before. In my
The latest (Jan 27th) changes to info/dir, i.e. its untabification
lead to the error
byte-code: No such node or anchor: top
when typing C-h i.
That's because in `Info-find-node-2' the regexp
\\(Node:\\|Ref:\\) *\\(top\\) *[, \n]
used for finding the top node does not match anymore.
--
* Eli Zaretskii (2006-01-24) writes:
From: Ralf Angeli [EMAIL PROTECTED]
Date: Tue, 24 Jan 2006 16:10:30 +0100
The build process aborts if `make info' is called with Texinfo 4.3.
[...]
This version comes with current MSYS and does not know @headitem which
was introduced with Texinfo 4.7
* Eli Zaretskii (2005-12-24) writes:
I installed a change that should fix this problem for you. Can you
sync with the repository and see if autoloads now work even with MSYS
munging of the command line?
Okay, now I tried again and creation of autoloads works. I checked
this with MinGW's
* Eli Zaretskii (2005-12-24) writes:
I installed a change that should fix this problem for you. Can you
sync with the repository and see if autoloads now work even with MSYS
munging of the command line?
Thanks for your efforts. I did a fresh checkout into a new directory,
ran `configure
* Eli Zaretskii (2005-12-18) writes:
However, I cannot accept your patch as it stands. First, you missed
the important WARNING in the comment just preceding the commands you
wanted to patch,
Oh great, then I'll probably have to do another upload to
alpha.gnu.org. At least because of the
* Ralf Angeli (2005-07-08) writes:
* Ralf Angeli (2005-07-07) writes:
Using this for bootstrapping with `mingw32-make bootstrap' from a DOS
prompt in the nt/ directory I get the following error:
[...]
Opening output file: invalid argument,
d:/software/windows/unix/src/emacs/lisp/D
* Reiner Steib (2005-12-15) writes:
On Wed, Dec 14 2005, Ralf Angeli wrote:
would it be possible for Emacs to figure out the right coding system
by itself in the case at hand? That means without me having to
specify coding systems explicitely by means of preferred coding
system options
There are some quoted lambda expressions in the manuals:
find . -type f -print0 | xargs -0 -e grep -nH -e '(lambda
./custom.texi:905: '(lambda ()
./custom.texi:1392: '(lambda ()
./custom.texi:: '(lambda () (auto-fill-mode 1)))
./emacs-xtra.texi:215: #'(lambda (optional
* David Hansen (2005-12-13) writes:
On Tue, 13 Dec 2005 13:12:02 +0100 Ralf Angeli wrote:
Attached you can find a file with two 8-bit characters I extracted
from a file produced by Visual Studio under Windows. The characters
should be u umlaut and the Euro sign. Emacs does not seem
* David Hansen (2005-12-14) writes:
On Tue, 13 Dec 2005 23:42:02 +0100 Ralf Angeli wrote:
| file code: 0xFC (encoded by coding system windows-1251-dos)
^
^
It for me it's
* Kim F. Storm (2005-12-08) writes:
Ralf Angeli [EMAIL PROTECTED] writes:
;; - use the SHIFT key with the prefix key, i.e. C-X or C-C
The last option does not seem to work (at least with the examples I
tried). As an example,
Thanks. I have installed a fix.
Thanks. I'll go and inform
Documentation of CUA mode in cua-base.el contains the following text:
;; If you really need to perform a command which starts with one of
;; the prefix keys even when the region is active, you have three options:
;; - press the prefix key twice very quickly (within 0.2 seconds),
;; - press the
submit
AUTH PLAIN base64-encoded credentials to the server.
With the following change to smtpmail.el I could be authenticated at
the SMTP server and send a mail:
2005-12-05 Ralf Angeli [EMAIL PROTECTED]
* mail/smtpmail.el (smtpmail-try-auth-methods): Send
credentials together
* David Reitter (2005-10-27) writes:
On 27 Oct 2005, at 02:31, Richard M. Stallman wrote:
A paragraph is NOT meant to be a single line, and if it appears as
one, that is very inconvenient.
Let me give you two examples.
- I've been doing some work in Python lately. Python enforces strict
* Juri Linkov (2005-10-25) writes:
Your patch doesn't look right. I think it is correct that
`show-paren-mode' indicates mismatches on escaped parentheses in
latex-mode, because according to the syntax table of latex-mode,
these parentheses are not matched. So when you type in latex-mode,
In LaTeX escaped parentheses like \(a^2+b^2=c^2\) are used for marking
inline math. `show-paren-mode' indicates mismatches when moving point
over the opening or closing parentheses. In order to prevent this, I
think, it should not try to match an escaped paren in the first place.
The following
With Transient Mark mode enabled I expected a section like
--8---cut here---start-8---
\section{foo}
Some text.
--8---cut here---end---8---
in a LaTeX buffer to be highlighted after typing `M-x
outline-mark-subtree RET'.
* Kim F. Storm (2005-07-15) writes:
For one thing, I introduced a redisplay loop that should be fixed now.
But fixing the loop meant that I had to eliminated part of the
original fix, so pls. test whether things still works ok.
Looks good. I could not find any regression.
--
Ralf
* Kim F. Storm (2005-07-13) writes:
I have installed some changes to fix this and other problems related
to line-move around such multi-line overlay strings.
Cool! Thank you very much! I was plowing through the code in xdisp.c
and dispnew.c but didn't really know where to start. Maybe I can
* Eli Zaretskii (2005-07-09) writes:
From: Ralf Angeli [EMAIL PROTECTED]
+ --eval $(ARGQUOTE)(let ((find-file-hook nil) \
+ (find-file-suppress-same-file-warnings t) \
+ (generated-autoload-file \
+ (expand
* Eli Zaretskii (2005-07-09) writes:
It's strange: MinGW-4.1.0.exe is under Current, but MinGW Runtime is
still at version 3.7. What is inside MinGW-X.Y.Z.exe---isn't it the
runtime plus the compiler and Binutils?
I don't remember what was packaged with it. And as I am currently
enjoying my
* Ralf Angeli (2005-07-07) writes:
Using this for bootstrapping with `mingw32-make bootstrap' from a DOS
prompt in the nt/ directory I get the following error:
[...]
Opening output file: invalid argument,
d:/software/windows/unix/src/emacs/lisp/D;C:Programmemsys☺.0
oftwarewindowsunix rc
* Ralf Angeli (2005-07-06) writes:
loaddefs.el in a Windows build checked out and compiled yesterday
doesn't seem to include all autoloads. For example the autoloads for
latexenc.el are missing. I suspect this is the cause for LaTeX files
in a Windows build of Emacs being opened with a raw
* Jason Rumney (2005-07-07) writes:
Can you please try to debug what has caused this on your machine. I do
not have this problem, and noone else has reported it either.
Okay, I inserted a `sleep 60' at the end of the `autoloads' target of
lisp/makefile and this is what I could observe during
* Jason Rumney (2005-07-07) writes:
The fact that you have no drive letters in the paths suggests to me that
you are using cygwin or msys make, which corrupts DOS paths to look like
unix paths in a way that only cygwin or msys tools can understand.
From my former message:
The version of
loaddefs.el in a Windows build checked out and compiled yesterday
doesn't seem to include all autoloads. For example the autoloads for
latexenc.el are missing. I suspect this is the cause for LaTeX files
in a Windows build of Emacs being opened with a raw-text-dos coding
system (which prevents
* Daniel Dehennin (2005-07-06) writes:
Le 4326 Septembre 1993, Lute Kamstra a tapoté:
(let ((s ONE TWO))
(string-match \\t\\(\\w+\\) s)
(replace-match (downcase (match-string 1 s)) t t s 1))
Well, in interactive replacement like query-replace-regexp, I can not
make lisp call in the
* Richard M. Stallman (2005-07-05) writes:
Besides GDB another easy to use testcase is ielm. Type `M-x ielm RET'
and press RET until the prompt reaches the bottom of the window.
When this happens point will be placed in the middle of the screen.
This problem does not happen for
* Kim F. Storm (2005-07-05) writes:
I would be VERY surprised if M-0 M-r suddenly started to scroll the
window.
What do you mean with started? Emacs 21 already behaves like this
in case `scroll-margin' has a non-zero value.
The description of `scroll-margin' in the Elisp manual also mentions
When `scroll-preserve-screen-position' is set to `always' Emacs
doesn't manage to keep the vertical position of point relative to
window boundaries if tall lines are involved. Here is a testcase:
(progn
(setq scroll-preserve-screen-position 'always)
(pop-to-buffer (get-buffer-create *test*))
* Richard M. Stallman (2005-07-02) writes:
at least broke scrolling of articles with RET in Gnus and makes
using GDB in Emacs (gud-mode) very inconvenient if the value of
`scroll-margin' is non-zero.
I don't use GNUS and I cannot test it.
Besides GDB another easy to use testcase
As far as I can see the changset
2005-06-25 Richard M. Stallman [EMAIL PROTECTED]
* macfns.c (Fx_show_tip): Pass new arg to try_window.
* w32fns.c (Fx_show_tip): Pass new arg to try_window.
* xfns.c (Fx_show_tip): Pass new arg to try_window.
* xdisp.c
* Kim F. Storm (2005-06-27) writes:
However, when I try it with the code above, it beeps in line-move-1
when I move backwards with C-p (for every 4th C-p or so). This is
because (one of the instances of) the following code is triggered.
(unless noerror
* Ralf Angeli (2005-06-16) writes:
After executing the code move point upwards with `C-p'. After point
hit the top of the window further movement will scroll the buffer line
by line. This will make the overlays disappear occasionally,
i.e. instead of the XXX\nXXX strings one will see
It seems that Emacs has problems keeping the display of multi-line
overlays correct when scrolling line by line. Here is an example you
can use in an Emacs started with `emacs -Q':
(progn
(switch-to-buffer (get-buffer-create *test*))
(set (make-local-variable 'scroll-conservatively) 1000)
* jhd (2005-06-12) writes:
This has been resolved now as a WONTFIX:
--- Additional Comments From Owen Taylor 2005-06-12 00:05 ---
This is working as intended - Pango has no real way of knowing that
you weren't writing greek text and thus wanted punctuation from the
greek font.
* Eli Zaretskii (2005-06-11) writes:
From: Ralf Angeli [EMAIL PROTECTED]
Date: Thu, 09 Jun 2005 00:52:54 +0200
On MS Windows the following code will generate a buffer which displays
aaa and after that a lot of whitespace. If you scroll around a bit
Emacs will hang with 100% CPU usage
* Lute Kamstra (2005-06-09) writes:
Ralf Angeli [EMAIL PROTECTED] writes:
emacs -Q -eval '(setq debug-on-error t)'
a debugger window with the following message pops up:
Debugger entered--Lisp error: (void-variable flyspell-mode)
Yesterday, I changed flyspell.el. As a result the var
* Richard Stallman (2005-06-05) writes:
Suppose you have a Makefile with the following contents:
FOO = bar \
xxx/xxx.xx xxx/xxx.xx
If you put the cursor at the start of the second line and type
`M-: (looking-at makefile-dependency-regex) RET' Emacs will enter an
* Jan D. (2005-06-06) writes:
This is a GTK thing, I can reproduce it with a tiny GTK program. If the
default font does not have the character (gamma) GTK tries another font
and that may look different than the default one. I am not sure why the
\ looks different though. I've filed a
AUCTeX calls `read-file-name' (and consequently `x-file-dialog') with
the string default as argument for the default file name. We have
various reports where this call, when invoked from a menu, led to a
loop which made Emacs unresponsive until `C-g' was typed. This
happens only under MS
After executing the following code
(easy-menu-define test-menu (current-local-map) doc
`(xxx
(,(concat (string (decode-char 'ucs 915)) \\Gamma))
(G \\Gamma)))
in an Emacs compiled with support for GTK menus, there will be a new
xxx menu with two entries. I expected the first menu
The new font locking code for Makefile mode produces a lot of errors
(see below in Recent messages) because of the element
(nil
(0 nil))
in `font-lock-keywords' which corresponds to
,(if negation
`(,negation (1 font-lock-negation-char-face prepend)
(2
* Stefan Monnier (2005-05-07) writes:
I expected the filter function to be called only when the menu is
being activated.
In many circumstances, the whole menu is computed even when the purpose is
only to refresh the menu-bar itself. This is not really considered as
a bug, just a
* Stefan Monnier (2005-05-07) writes:
Hm, this might be a knock-out criterion for the usage of menu filters
or hooks in order to ask the user for a master file of a multi-file
LaTeX document.
Indeed. Why do you want to do it from a menu-filter? It sounds like an odd
idea to start with.
* Kim F. Storm (2005-04-27) writes:
Ralf Angeli [EMAIL PROTECTED] writes:
The symptoms are the following: When pressing mouse-2 on a misspelled
word, the flyspell menu will appear as soon as mouse-2 is released and
will stay opened. I can close it again by clicking with mouse-1
somewhere
* Christian Schlauer (2005-04-12) writes:
[BibTeX keys]
There is one more questionmark, though: should these keys contain
non-ASCII characters?
[...]
So it would be safer to ``strip accents'', I guess?
You can customize `bibtex-autokey-name-change-strings' for this
purpose:
,
|
* David PONCE (2005-04-05) writes:
It looks clean to me. I have never understood widgets very well,
so I don't know whether it is correct. But if it seems to work
better than the present code, it must be a step forward.
I wish someone here had enough expertise to be able to
assure us it
If you have flyspell-mode enabled, click with mouse-2 on a highlighted
word not in the dictionary and choose Save word. After that, text
currently in the kill ring will be yanked into the buffer.
This was probably introduced by changing mouse-2 to down-mouse-2 in
`flyspell-mode-map' because the
[I haven't received an email of your answer, so I am replying via
Gmane.]
* Stefan Monnier (2005-03-27) writes:
(setq font-lock-keywords '((foo . bold)))
This shouldn't be a face symbol but an expression (whose value is typically
a face
Executing the following example code
(with-temp-buffer
(insert foo)
(setq font-lock-keywords '((foo . bold)))
(font-lock-fontify-keywords-region (point-min) (point-max)))
will result in an error that the variable `bold' is void. If you use,
for example, `font-lock-comment-face' instead of
There are some small mistakes in the Elisp manual's description of
`remove-list-of-text-properties'. I think the description should look
like this:
--- text.texi 07 Mar 2005 16:48:51 +0100 1.95
+++ text.texi 11 Mar 2005 08:34:59 +0100
@@ -2619,9 +2619,9 @@
@end defun
@defun
* Kenichi Handa (2005-03-09) writes:
In article [EMAIL PROTECTED], Dave Love [EMAIL PROTECTED] writes:
The guillemets , , and should all be punctuation. The single
ones currently have word syntax, and the double ones are treated as
parens in latin-{1,5,9}.el.
As I don't use those
As I am not really a fan of mouse-2 I was very delighted that support
for mouse-1 clicks on certain links was added. Now after using it for
quite some time I must say that I tend to revert to mouse-2 because
clicking with mouse-1 succeeds in only about 50% of cases for me.
One reason for this is
* Ralf Angeli (2005-02-28) writes:
[menu-bar-update-hook]
I will update the documentation. Meanwhile, do you think
the current behavior is a problem?
If people deduct from the current doc string that the hook is only
called when the menubar is used, this could make them disregard
* Kim F. Storm (2005-02-22) writes:
Ralf Angeli [EMAIL PROTECTED] writes:
(let (ov)
(insert \n\nxxx)
(setq ov (make-overlay (line-beginning-position) (point)))
(overlay-put ov 'mouse-face 'highlight)
(overlay-put ov 'display yyy))
Okay, I poked around a bit and the following
* David Kastrup (2005-02-18) writes:
Does the following patch fix it?
Yes, it does. Thanks!
--
Ralf
___
Emacs-pretest-bug mailing list
Emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
99 matches
Mail list logo
