emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ken Mankoff <mankoff@gmail.com>
To: Aaron Ecay <aaronecay@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>, Rasmus <rasmus@gmx.us>
Subject: Re: Bug: CAPTION space after 70th character (8.2.7c-71-g60418c-elpa)
Date: Sat, 27 Sep 2014 23:45:27 -0400	[thread overview]
Message-ID: <m2vbo8s90o.fsf@gmail.com> (raw)
In-Reply-To: <87d2agmua1.fsf@gmail.com>


* On 2014-09-27 at 21:02, Aaron Ecay wrote:
> Hi Ken,
>
> 2014ko irailak 27an, Ken Mankoff-ek idatzi zuen:
>>> How about setting debug-on-quit and hitting C-g when the prompt shows
>>> up?
>> 
>> Still nothing in *Messages*. I know this is related to fill-paragraph,
>> because that triggers this too, even if used below the CAPTION
>> line. CAPTION doesn't let fill-paragraph do its thing, which I assume
>> is part of the issue.
>
> Odd; my suggestion should have given you a backtrace after hitting C-g,
> but I guess for some reason it didn’t work.
>
> Since you can trigger the undesired behavior with fill-paragraph, what
> about using edebug (info "(elisp) Edebug") to instrument that function
> and then stepping through to see where the prompt is triggered?

Triggered by the line (funcall function justify)

I find it strange that y'all can't re-create this since I can do it with
emacs -Q, although perhaps it is specific to the emacs-mac port. I'm
happy to keep following instructions and dig deeper, but this is way
outside the scope of my emacs/elisp skills. I'm happy to just invoke new
frames with C-x 5 2 rather than emacsclient to work around this for now.

  -k.

  reply	other threads:[~2014-09-28  3:45 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
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 [this message]
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=m2vbo8s90o.fsf@gmail.com \
    --to=mankoff@gmail.com \
    --cc=aaronecay@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).