From: Ken Mankoff <mankoff@gmail.com>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: CAPTION space after 70th character (8.2.7c-71-g60418c-elpa)
Date: Fri, 26 Sep 2014 12:50:47 -0400 [thread overview]
Message-ID: <m2vboa9vh4.fsf@gmail.com> (raw)
In-Reply-To: <87d2aiv0nt.fsf@gmx.us>
* On 2014-09-26 at 11:53, Rasmus wrote:
> Ken Mankoff <mankoff@gmail.com> writes:
>> If I have a #+CAPTION line, I can type my figure caption as I would
>> expect. But as soon as I pass the 70th column, the spacebar triggers
>> an error. I can type letters after the 70th column, but not a
>> space. When I press the spacebar on the 70th or higher column, the
>> mini-buffer says:
>>
>> Buffer ` *temp*-624801' still has clients; kill it? (y or n)
>>
>
> I can't reproduce using the latest version of org.
>
> Does this happen when you start Emacs with emacs -q? If not, it could
> be some third-party package causing the error.
>
> Try also M-x toggle-debug-on-error and make the error reappear. This
> should give insights in where the error occurs.
>
debug-on-error doesn't help because there isn't actually an error as far
as I can tell. It is a bug, not an error. Nothing shows up in *Messages*
I've isolated the problem to this line:
(add-hook 'text-mode-hook 'turn-on-auto-fill)
Which I've had enabled for a long time, but has only recently been
causing issues with CAPTION lines. I can re-create it only when that
line is uncommented.
Oddly, even the re-creation is complicated. I can't get the bug to show
up in the primary window. I must launch a second frame. I can re-create
it like this:
$ /usr/local/Cellar/emacs-mac/emacs-24.3-mac-4.8/bin/emacs -Q
load Org
M-x auto-fill-mode
#+CAPTION lots of text and spaces does not cause bug
$ /usr/local/Cellar/emacs-mac/emacs-24.3-mac-4.8/bin/emacsclient -c foo.org
#+CAPTION and now the bug exists after line 70
It doesn't appear if I open a new frame with "C-x 5 2", only if I open a
new frame with emacsclient from the command line.
Some more strange behavior: If the bug appears and I close the frame,
and then open the file again (find-file foo.org), the file (a massive
ORG file) appears as "*temp*" in the modeline and the contents of the
file are only the 1 line of the caption. If I kill buffer *temp* and
then find-file again, the contents are correctly loaded.
-k.
next prev parent reply other threads:[~2014-09-26 16:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 15:05 Bug: CAPTION space after 70th character (8.2.7c-71-g60418c-elpa) Ken Mankoff
2014-09-26 15:53 ` Rasmus
2014-09-26 16:50 ` Ken Mankoff [this message]
2014-09-27 19:27 ` Aaron Ecay
2014-09-28 0:20 ` Ken Mankoff
2014-09-28 1:02 ` Aaron Ecay
2014-09-28 3:45 ` Ken Mankoff
2014-09-28 4:27 ` Ken Mankoff
2014-09-28 4:41 ` Ken Mankoff
2014-09-28 17:20 ` Ken Mankoff
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2vboa9vh4.fsf@gmail.com \
--to=mankoff@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).