I can confirm that inserting the backslash before the semicolon as
suggested works for me.
--
forward-sexp parses character literal ?; as comment
https://bugs.launchpad.net/bugs/405498
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
With this .emacs file I am able to reproduce the error. The error
message implicates the tex-mode-hook stanza which begins on line 195 of
the .emacs file. Apparently forward-sexp cannot cope with the character
literal for a literal semicolon character, which I think is a bug if
Emacs doesn't othe
On 02/08/2009, era wrote:
> Is this somehow specific to KDE? Does it matter whether you use the
> keyboard or the mouse to select the "Dismiss this startup screen" link?
> Do you have anything in your .emacs file which could be causing this?
> (Can you create a shell script which runs emacs -q,
Thanks for the repro steps. I still do not get the error message, but I
do see the "Dismiss this startup screen [ ] Never show it again." text
at the end of the *GNU Emacs* buffer. (For testing, I picked the
application/zip attachment from
http://sprott.physics.wisc.edu/viewtest.htm and selected
The problem does not occur when emacs is opened without a file, nor
when it is called from the command line, in these cases, it just comes
up with a single buffer shown (*Scratch* or the file).
It does occur whenever I click on a file whose type is bound to emacs,
or select "open with > emacs22 (X
I'm afraid I don't see how to reproduce this with emacs22. What do you
see and what did you do when you started Emacs in order to see this?
More to the point, if you can reproduce this every time you run Emacs,
do you think you could do the following, please? Run Emacs with the
following:
bash$
