From: cberry@tajo.ucsd.edu
To: emacs-orgmode@gnu.org
Subject: Re: Auto-fill-mode with code sections
Date: Fri, 04 May 2012 21:07:26 -0700 [thread overview]
Message-ID: <87bom36zk1.fsf@tajo.ucsd.edu> (raw)
In-Reply-To: 87y5p77lo4.fsf@gmx.com
Eric Schulte <eric.schulte@gmx.com> writes:
> Ken Williams <Ken.Williams@windlogics.com> writes:
>
>> Ping - I'm still interested in this, if anyone has any recommendations. Thanks.
>>
>
> Hi Ken,
>
> I don't know of an automatic solution here. One option is to edit code
> sections with org-edit-special, i.e., press C-c ' from within a code
> block.
>
> Best,
Here is a start.
It fills normal text, but leaves src blocks alone.
Maybe add something to one of the org-mode hooks ?
HTH,
Chuck
,----
|
| * autofill, but not src blocks
|
| #+begin_src emacs-lisp
| (defun org-auto-fill-function ()
| "auto fill function to leave src blocks alone"
| (if (not (org-babel-get-src-block-info))
| (do-auto-fill)))
| (setq normal-auto-fill-function 'org-auto-fill-function)
| #+end_src
|
|
| aaa aaa vvv aaa aaa vvv aaa aaa vvv aaa aaa vvv aaa aaa vvv aaa aaa
| aaa aaa vvv aaa aaa vvv aaa aaa vvv aaa aaa vvv aaa aaa vvv aaa aaa
| vvv aaaaaa vvv aaa aaa vvv
|
| #+begin_src R
| x <- y + 1 + 2 + 1 + 2 + 1 + 2 + 1 + 2 + 1 + 2 + 1 + 2 + 1 + 2 + 1 + 2 + 1 + 2 + 1 + 2 + 3
| #+end_src
`----
>
>>
>> -Ken
>>
>>> From: Ken Williams
>>> Sent: Tuesday, May 01, 2012 8:51 AM
>>> To: emacs-orgmode@gnu.org
>>> Subject: Auto-fill-mode with code sections
>>>
>>> Hi,
>>>
>>> I use org-mode extensively with R code sections, as a scientific notebook.
>>> One annoyance I have is that when I have auto-fill-mode turned on (which
>>> is convenient for the main body parts of the document), it extends to the
>>> code section and starts auto-filling my code.
>>>
>>> Can anyone recommend a configuration that will get me folding in the body
>>> sections, but not in the code sections? It could use another mechanism
>>> besides auto-fill-mode if that's what's preferred these days, but auto-fill-mode
>>> is the one I'm familiar with.
>>
>>
>> CONFIDENTIALITY NOTICE: This e-mail message is for the sole use of the
>> intended recipient(s) and may contain confidential and privileged
>> information. Any unauthorized review, use, disclosure or distribution
>> of any kind is strictly prohibited. If you are not the intended
>> recipient, please contact the sender via reply e-mail and destroy all
>> copies of the original message. Thank you.
>>
--
Charles C. Berry Dept of Family/Preventive Medicine
cberry at ucsd edu UC San Diego
http://famprevmed.ucsd.edu/faculty/cberry/ La Jolla, San Diego 92093-0901
next prev parent reply other threads:[~2012-05-05 4:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 22:00 Auto-fill-mode with code sections Ken Williams
2012-05-04 20:09 ` Eric Schulte
2012-05-05 4:07 ` cberry [this message]
2012-05-05 6:17 ` Bastien
-- strict thread matches above, loose matches on Subject: below --
2012-05-01 13:51 Ken Williams
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=87bom36zk1.fsf@tajo.ucsd.edu \
--to=cberry@tajo.ucsd.edu \
--cc=emacs-orgmode@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 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).