visual-fill-column-mode with org

visual-fill-column-mode with org

[Vikas Rawal]

I would like to use visual-fill-column-mode with my org files. However, this has a peculiar problem that org tables also start wrapping at fill-column. Does anyone use visual-fill-column-mode with org and has found a way of telling it to ignore lines starting with a |?

Thanks,

Vikas

Re: visual-fill-column-mode with org

[Rasmus]

Vikas Rawal <vikaslists@agrarianresearch.org> writes:

> I would like to use visual-fill-column-mode with my org
> files. However, this has a peculiar problem that org tables also start
> wrapping at fill-column. Does anyone use visual-fill-column-mode with
> org and has found a way of telling it to ignore lines starting with a
> |?

Hardly a solution, but you can force columns to only be a certain width
with the <n> declaration, where n is an integer.

Rasmus

-- 
A clever person solves a problem. A wise person avoids it

Re: visual-fill-column-mode with org

[Vikas Rawal]

> 
>> I would like to use visual-fill-column-mode with my org
>> files. However, this has a peculiar problem that org tables also start
>> wrapping at fill-column. Does anyone use visual-fill-column-mode with
>> org and has found a way of telling it to ignore lines starting with a
>> |?
> 
> Hardly a solution, but you can force columns to only be a certain width
> with the <n> declaration, where n is an integer.
> 

Reducing width of the table to fill-column is hardly usable. It will not work if I zoom in.

Also, I will have to keep doing this for every table. Everything will get more complicated if the table is result of a babel code block.

No..

Vikas

Re: visual-fill-column-mode with org

[Aaron Ecay]

Hi Vikas,

AFAIK, the visual-fill-mode features are implemented at a very low level
in the display code, in C.  It would be nice if it was possible to mark
lines as exempt from wrapping (e.g. by putting a text property on
them).  Org could then arrange for tables to have this text property,
and not be wrapped.  But this would require changes to emacs’s C code.
(I’m also not sure how it would interact with visual-fill-column-mode,
which is a third-party addon.)

Another option would be to use auto-fill-mode to keep your text
paragraphs within your desired width, without affecting tables.

-- 
Aaron Ecay

Re: visual-fill-column-mode with org

[Vikas Rawal]

[-- Attachment #1: Type: text/plain, Size: 786 bytes --]


> Another option would be to use auto-fill-mode to keep your text
> paragraphs within your desired width, without affecting tables.
> 

I do not like auto-fill-mode inserting hard returns at fill-column. This creates problems for version control, as sentences cannot be correctly identified.

I would like each sentence to be on a single line, wrapped only for visual effect, without having hard-returns, so that git can correctly identify changes in each sentence.

That is the reason I am looking at visual-fill-column-mode.

Joost Kremers, author of visual-fill-column-mode, says that this would not be possible since "visual-fill-column-mode does not really do any filling / wrapping”.

So, at the moment, we really do not have any appropriate solution.

Vikas


[-- Attachment #2: Type: text/html, Size: 1518 bytes --]

Re: visual-fill-column-mode with org

[Vikas Rawal]

[-- Attachment #1: Type: text/plain, Size: 786 bytes --]


> Another option would be to use auto-fill-mode to keep your text
> paragraphs within your desired width, without affecting tables.
> 

I do not like auto-fill-mode inserting hard returns at fill-column. This creates problems for version control, as sentences cannot be correctly identified.

I would like each sentence to be on a single line, wrapped only for visual effect, without having hard-returns, so that git can correctly identify changes in each sentence.

That is the reason I am looking at visual-fill-column-mode.

Joost Kremers, author of visual-fill-column-mode, says that this would not be possible since "visual-fill-column-mode does not really do any filling / wrapping”.

So, at the moment, we really do not have any appropriate solution.

Vikas


[-- Attachment #2: Type: text/html, Size: 1584 bytes --]