Start Emacs with
emacs -q -no-site-file -f transient-mark-mode -f toggle-debug-on-error foo.mp
Then click with the mouse pointer onto the "Meta" menu. The result is
this backtrace:
Debugger entered--Lisp error: (mark-inactive)
signal(mark-inactive nil)
mark()
meta-mark-active()
In GNU E
* 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
Copying
(let (ov)
(insert "\n\nxxx")
(setq ov (make-overlay (line-beginning-position) (point)))
(overlay-put ov 'mouse-face 'highlight)
(overlay-put ov 'display "yyy"))
into the *scratch* buffer and typing `C-x C-e' with point at the last
parenthesis, you will see the string "yyy" further
* Ralf Angeli (2005-02-19) writes:
> Copying
>
> (let (ov)
> (insert "\n\nxxx")
> (setq ov (make-overlay (line-beginning-position) (point)))
> (overlay-put ov 'mouse-face 'highlight)
> (overlay-put ov 'display "yyy"))
>
> in
* 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
The doc string of `menu-bar-update-hook' states that it is a "... hook
run for clicks on menu bar, before displaying a submenu."
Execute the following code snippet:
(progn
(setq hook-counter 0)
(add-hook 'menu-bar-update-hook
(lambda ()
(setq hook-counter (1+ hook-co
* Richard Stallman (2005-02-27) writes:
> The doc string of `menu-bar-update-hook' states that it is a "... hook
> run for clicks on menu bar, before displaying a submenu."
>
> I think the doc string is mistaken. Every substantial redisplay runs
> this hook since every substantial redispl
* 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 coul
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
* Kim F. Storm (2005-03-08) writes:
> Ralf Angeli <[EMAIL PROTECTED]> writes:
>
>> The second reason is the delay until the action associated with the
>> click is actually performed and that one has to keep the mouse pointer
>> over the link in order for the action
* 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
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 rem
icomplete-mode somehow deactivates an activated region when
transient-mark-mode is active. In order to see this behavior, start
Emacs with `emacs -Q' and copy the following function into the
*scratch* buffer.
(defun foo ()
(interactive)
(icomplete-mode 1)
(transient-mark-mode 1)
(set-mark
* Stefan Monnier (2005-03-21) writes:
>> icomplete-mode somehow deactivates an activated region when
>> transient-mark-mode is active. In order to see this behavior, start
>> Emacs with `emacs -Q' and copy the following function into the
>> *scratch* buffer.
>
>> (defun foo ()
>> (interactive)
* Stefan Monnier (2005-03-21) writes:
>> This problem currently prevents AUCTeX users from marking LaTeX
>> environments as long as icomplete-mode is active.
>
> It only prevents them if they use M-x ..., not if they use a key-binding to
> mark the environment, right?
Yes.
> Does the patch below
* Richard Stallman (2005-03-22) writes:
> I think the right answer is to make deactivate-mark buffer-local.
>
> That might be right, but it is too radical for now.
> There are hundreds of places that it might break, and surely
> some of them will break.
>
> You can always fix these problems lo
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
[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
* Miles Bader (2005-03-28) writes:
> On Mon, 28 Mar 2005 10:00:55 +0200, Ralf Angeli <[EMAIL PROTECTED]> wrote:
>>
>> Does this mean using an expression is the canonical way of referring
>> to faces in `font-lock-keywords' and using a symbol is only supp
* Miles Bader (2005-03-28) writes:
> On Mon, 28 Mar 2005 11:09:16 +0200, Ralf Angeli <[EMAIL PROTECTED]> wrote:
>> > No, it's just an expression -- for the standard font-lock faces there
>> > are variable names that are _exactly_ the same as the face n
[Limiting list of recipients to emacs-pretest-bugs.]
* David Ponce (2005-03-27) writes:
> In latest CVS Emacs the "Inherit" face attribute appears as a
> "Function" widget in the `customize-face' buffer.
>
> In Emacs 21.3 it appears as expected, that is a "Face" widget allowing
> to customize the
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
* Stefan Monnier (2005-04-01) writes:
>> 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-
Trying to set up nxml-mode I was bitten by `magic-mode-alist'. The
installation instructions of the mode tell you to change
`auto-mode-alist' in order to load the mode for the specified file
endings. This works fine with new files but fails on some existing
files I have. The problem is that `aut
* 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
>> as
* Ralf Angeli (2005-04-06) writes:
> I just compared this functionality in CVS Emacs with Emacs 21. In
> Emacs 21 it is easier to select a face because there is this "Select
> Face" button which presents you with a minibuffer prompt including
> auto-completion of face na
* 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:
,
| bibtex
* Stefan Monnier (2005-04-01) writes:
> Oh, I can reproduce it:
> The problem seems to be in the mouse-drag-region code.
>
> You have to do:
>
> - press mouse-1 somewhwere
> - drag to select a region
> - release mouse-1
> - move mouse to the word with bad spelling
> - press mou
* 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
While fiddling with the menu filters in AUCTeX I ran into a problem
with the filter functions being called too early, i.e. during the
execution of `easy-menu-define'. This happens only if
`easy-menu-define' is called in a load file. You can use the
following call for testing:
(easy-menu-define n
* 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 mis
* 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
* Stefan Monnier (2005-05-07) writes:
>> So we searched for a way to delay the question about the master file
>> until this information is actually needed in the editing process. One
>> of these events is when the user opens the menu for inserting a LaTeX
>> environment or macro.
>
> I understand
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 font-
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
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
infinite loop.
I noticed this while trying to generate a change l
Suppose you want to type the following lines into a new Makefile:
FOO = bar \
bar \
bar
If you type everything by hand from top to bottom, as soon as is
typed on the third line, fontification of the second line will
disappear. Content typed in the third line will not be fontifie
AUCTeX calls `read-file-name' (and consequently `x-file-dialog') with
the string "" 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 Windows.
The
* 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 ente
* Richard Stallman (2005-06-05) writes:
> I think the only feasible fix for this problem is to turn off the new
> feature of highlighting the value assigned to the make macro, and go
> back to highlighting only the macro name.
>
> It is sort of unfortunate, but I don't know how to fix it any bette
* 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
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. Typing `C-g' does not help.
(progn
(pop-to-buffer (get-buffer-create "*test*"))
(insert "aaa\nbbb\nccc\n")
(let (
If Emacs is started with
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)
In GNU Emacs 22.0.50.1 (i686-pc-linux-gnu, GTK+ Version 2.6.4)
of 2005-06-09 on neutrino
Distributor `The XFree86
* 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 flyspe
* 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 s
* 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 fo
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)
* 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
* David Moffat (2005-06-19) writes:
> in the CVS version (number above) that I got about a month or two back,
> there is a bug in the code that makes font-locking barf on
> a LaTeX file, e.g., where a line is commented out.
>
> So in the lines in some LaTeX file:
>
> \textbf{foo}
> %\textbf{bar}
>
* 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
>
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 (try_w
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 (try_w
* Richard M. Stallman (2005-07-02) writes:
> at least broke scrolling of articles with 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 testcas
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-05) writes:
> Besides GDB another easy to use testcase is ielm. Type `M-x ielm RET'
> and press 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 menti
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 ch
* Daniel Dehennin (2005-07-06) writes:
> Le 4326 Septembre 1993, Lute Kamstra a tapoté:
>> (let ((s "ONE TWO"))
>> (string-match "\\> (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 replace
* 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 be
* 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
* 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
>
* 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) \
>> +
* 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
enjoyin
* Richard Stallman (2005-06-17) writes:
> I wrote this patch which makes line-move-1 use vertical motion when
> overlays are around. It fixes the reported bug, but the display bug
> is still there: using goto-char to move to position 3011 (when that
> was above the screen) makes the overlays disa
Some additions ...
* Ralf Angeli (2005-07-10) writes:
> I am currently not sure if `line-move-1' is the correct location for
> fixing this bug. Maybe the code involved in scrolling would be more
> appropriate?
With the testcase one can demonstrate the problems with scrollin
* 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 ca
* 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
___
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'.
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 pa
* 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
* 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 enfor
* Juri Linkov (2005-10-27) writes:
>> To me it looks like the syntax table is fine, but `forward-sexp'
>> (i.e. `scan_lists') is disregarding it.
>
> How do you think `scan_lists' should treat a character quote?
> I think that when point is after it, then `scan_lists' should work
> as if point was
* David Reitter (2005-10-27) writes:
> On 27 Oct 2005, at 16:27, Ralf Angeli wrote:
>>>
>>> - I've been doing some work in Python lately. Python enforces strict
>>> formatting, and you don't have the option of inserting a newline at
>>> almos
hat means instead of "AUTH PLAIN" smtpmail.el should submit
"AUTH PLAIN " 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-a
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 pre
sonally I don't agree because
it's likely to be useful (especially for people coming from vi) and
even has its own keybinding. It should not be hidden from the user.
So what about the following patch for the Emacs manual?
2005-12-08 Ralf Angeli <[EMAIL PROTECTED]>
*
* 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,
>
> Thank
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 to be able
to find the right coding system for it and displays it with
raw-text-dos. I could not get th
* 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 si
* 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)
>^
>
* Ralf Angeli (2005-12-14) writes:
> * David Hansen (2005-12-14) writes:
>
>> file code: 0xFC (encoded by coding system windows-1252-unix)
>
> Argh, yes, that was the problem. Not so much a typo, I simply used
> the wrong coding system. Thanks for setting me right (twic
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 noconf
* 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 prefe
* 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,
>&
* 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 u
* Eli Zaretskii (2005-12-19) writes:
>> From: Ralf Angeli <[EMAIL PROTECTED]>
>>
>> Oh great, then I'll probably have to do another upload to
>> alpha.gnu.org.
>
> Sorry, I'm confused: what upload to alpha.gnu? What did you upload
> there, an
* 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-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 m
The build process aborts if `make info' is called with Texinfo 4.3.
Here is the build output:
$ make info
[Please ignore a syntax error on the next line - it is intentional]
/bin/sh.exe: -c: line 1: unexpected EOF while looking for matching `"'
/bin/sh.exe: -c: line 2: syntax error: unexpected end
* 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 kn
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.
--
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 case there
are no changes written to t
* 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 befo
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*"))
(inser
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 starte
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 tim
* 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
A
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
notic
* Eli Zaretskii (2006-04-08) writes:
>> From: Ralf Angeli <[EMAIL PROTECTED]>
>> Date: Sat, 08 Apr 2006 21:23:21 +0200
>>
>> When starting Emacs with
>>
>> emacs -Q -f toggle-debug-on-error test.c
>>
>> the following error occurs:
>>
1 - 100 of 153 matches
Mail list logo
