From: Kevin Ryde <user42_kevin@yahoo.com.au>
To: 19326@debbugs.gnu.org
Subject: bug#19326: 24.4; tex-validate-buffer error "Buffer is read-only"
Date: Tue, 09 Dec 2014 18:07:58 +1100 [thread overview]
Message-ID: <877fy1712p.fsf@blah.blah> (raw)
Running
emacs -Q /tmp/foo.tex
M-x tex-validate-buffer
=>
error: Buffer is read-only: #<buffer *Occur*>
I hoped it would say something, or nothing, about the buffer -- an empty
buffer in this case.
It looks like occur-mode may set the occur buffer read-only which
tex-validate-buffer doesn't expect when writing its output there.
In GNU Emacs 24.4.1 (i586-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
of 2014-10-26 on x86-csail-01, modified by Debian
Configured using:
`configure --build i586-linux-gnu --prefix=/usr
--sharedstatedir=/var/lib --libexecdir=/usr/lib
--localstatedir=/var/lib --infodir=/usr/share/info
--mandir=/usr/share/man --with-pop=yes
--enable-locallisppath=/etc/emacs24:/etc/emacs:/usr/local/share/emacs/24.4/site-lisp:/usr/local/share/emacs/site-lisp:/usr/share/emacs/24.4/site-lisp:/usr/share/emacs/site-lisp
--build i586-linux-gnu --prefix=/usr --sharedstatedir=/var/lib
--libexecdir=/usr/lib --localstatedir=/var/lib
--infodir=/usr/share/info --mandir=/usr/share/man --with-pop=yes
--enable-locallisppath=/etc/emacs24:/etc/emacs:/usr/local/share/emacs/24.4/site-lisp:/usr/local/share/emacs/site-lisp:/usr/share/emacs/24.4/site-lisp:/usr/share/emacs/site-lisp
--with-x=yes --with-x-toolkit=lucid --with-toolkit-scroll-bars
--without-gconf --without-gsettings 'CFLAGS=-g -O2
-fstack-protector-strong -Wformat -Werror=format-security -Wall'
CPPFLAGS=-D_FORTIFY_SOURCE=2 LDFLAGS=-Wl,-z,relro'
Important settings:
value of $LANG: en_AU.utf8
locale-coding-system: utf-8-unix
next reply other threads:[~2014-12-09 7:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 7:07 Kevin Ryde [this message]
2015-09-23 11:34 ` bug#19326: 24.4; tex-validate-buffer error "Buffer is read-only" phs
2020-08-12 16:55 ` Stefan Kangas
2021-07-13 18:13 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877fy1712p.fsf@blah.blah \
--to=user42_kevin@yahoo.com.au \
--cc=19326@debbugs.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.