emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nicolas Goaziou <n.goaziou@gmail.com>
To: "R. Michael Weylandt" <michael.weylandt@gmail.com>
Cc: Bastien <bzg@gnu.org>, "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Prepare release 8.2.6
Date: Sat, 05 Apr 2014 21:18:24 +0200	[thread overview]
Message-ID: <87y4zj60vz.fsf@gmail.com> (raw)
In-Reply-To: <CAAmySGP58A_tVoGq_WM0mfGaLWDOCvBpw7yoxf=8i081BsPtgw@mail.gmail.com> (R. Michael Weylandt's message of "Sat, 5 Apr 2014 12:41:25 -0400")

Hello,

"R. Michael Weylandt" <michael.weylandt@gmail.com> writes:

>> 1) Tell Emacs not to break inline source blocks when filling paragraphs:
>>
>> http://lists.gnu.org/archive/html/emacs-orgmode/2014-03/msg01310.html
>
> Small patch in support:

Thank you.

> +(defun org-in-inline-src-block-p ()
> +  "Test if within an inline src block."
> +  (org-in-regexp org-babel-inline-src-block-regexp))

I suggest not to use `org-in-regexp' here but `org-element-context'.

> -               org-fill-paragraph-with-timestamp-nobreak-p)))))
> +               org-fill-paragraph-with-timestamp-nobreak-p
> +               org-in-inline-src-block-p)))))

Besides inline source blocks, ISTR there was other places where filling
was inappropriate (verbatim, code, export snippet, macro...). A single
`org-element-context' will find them all.

Another option for the problem at hand is to simply remove newline
characters in inline source blocks before executing them.


Regards,

-- 
Nicolas Goaziou

next prev parent reply	other threads:[~2014-04-05 19:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-03  6:37 Prepare release 8.2.6 Bastien
2014-04-04  9:05 ` Sebastien Vauban
2014-04-04 11:51 ` Michael Weylandt
2014-04-05 16:41   ` R. Michael Weylandt
2014-04-05 19:18     ` Nicolas Goaziou [this message]
2014-04-07  1:48       ` R. Michael Weylandt
2014-04-07 10:19         ` Nicolas Goaziou
2014-04-17 19:58           ` Bastien
2014-04-04 14:32 ` Michael Weylandt
2014-04-05 16:45   ` R. Michael Weylandt
2014-04-05 19:27     ` Nicolas Goaziou
2014-04-05 21:48       ` York Zhao
2014-04-06 17:51       ` R. Michael Weylandt
2014-04-06 18:03         ` Nicolas Goaziou
2014-04-11  2:43         ` Eric Schulte
2014-04-13 17:02           ` R. Michael Weylandt
2014-04-17  6:26             ` Bastien
  -- strict thread matches above, loose matches on Subject: below --
2014-04-03  7:53 Bastien
2014-04-03  9:17 ` Alan Schmitt
2014-04-03 10:13 ` KDr2
2014-04-03 11:47 ` Rainer M Krug
2014-04-03 11:47 ` Rainer M Krug
2014-04-18 12:04   ` Bastien
2014-04-28 13:40     ` Rainer M Krug

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=87y4zj60vz.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=michael.weylandt@gmail.com \
    /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

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).