emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jeff Horn <jrhorn424@gmail.com>
To: "Filippo A. Salustri" <salustri@ryerson.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: question about indirect buffers for capture and line-breaks
Date: Thu, 24 Feb 2011 11:09:12 -0500	[thread overview]
Message-ID: <AANLkTin0iQz0P41Vh1ahDAYLYG1OvkAQWxRhBn-VsNqJ@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=vH_aWKPxkdhZxpCBNLG4DcyEu7hV4b14DjWQx@mail.gmail.com>

Yep.

Evaluate the following two lines in the scratch buffer:

    (auto-fill-mode -1)
    (auto-fill-mode nil)

The first returns nil every time. The second returns true every time. Funky.

On Thu, Feb 24, 2011 at 11:07 AM, Jeff Horn <jrhorn424@gmail.com> wrote:
> What happens if you use (auto-fill-mode -1) intead?
>
> ,----[ C-h f auto-fill-mode RET ]
> | auto-fill-mode is an interactive compiled Lisp function in
> | `simple.el'.
> |
> | (auto-fill-mode &optional ARG)
> |
> | Toggle Auto Fill mode.
> | With ARG, turn Auto Fill mode on if and only if ARG is positive.
> | In Auto Fill mode, inserting a space at a column beyond `current-fill-column'
> | automatically breaks the line at a previous space.
> |
> | The value of `normal-auto-fill-function' specifies the function to use
> | for `auto-fill-function' when turning Auto Fill mode on.
> `----
>
> I think "nil" counts as a positive number. Maybe that's a bug? I dunno.
>
> On Thu, Feb 24, 2011 at 7:33 AM, Filippo A. Salustri
> <salustri@ryerson.ca> wrote:
>> Hi,
>> I've turned off hard line breaks for various reasons.  I do it like this:
>>>
>>> (add-hook 'org-mode-hook
>>>           '(lambda ()
>>>              (auto-fill-mode nil)
>>>              (visual-line-mode t)))
>>
>> However, in the indirect buffers used by capture, hard line breaks are still
>> in place.
>> I've looked, but can't find an explanation of how to control this.
>> Can anyone advise me?
>> Cheers.
>> Fil
>>
>> --
>> Filippo A. Salustri, Ph.D., P.Eng.
>> Mechanical and Industrial Engineering
>> Ryerson University
>> 350 Victoria St, Toronto, ON
>> M5B 2K3, Canada
>> Tel: 416/979-5000 ext 7749
>> Fax: 416/979-5265
>> Email: salustri@ryerson.ca
>> http://deseng.ryerson.ca/~fil/
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Please use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>
>>
>
>
>
> --
> Jeffrey Horn
> http://www.failuretorefrain.com/jeff/
>



-- 
Jeffrey Horn
http://www.failuretorefrain.com/jeff/

  reply	other threads:[~2011-02-24 16:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24 12:33 question about indirect buffers for capture and line-breaks Filippo A. Salustri
2011-02-24 16:07 ` Jeff Horn
2011-02-24 16:09   ` Jeff Horn [this message]
2011-02-24 16:41     ` Filippo A. Salustri

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=AANLkTin0iQz0P41Vh1ahDAYLYG1OvkAQWxRhBn-VsNqJ@mail.gmail.com \
    --to=jrhorn424@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=salustri@ryerson.ca \
    /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).