auto-fill bug

auto-fill bug

[Adam Spiers]

I just found some strange behaviour with auto-fill mode on:

--------- 8< --------- 8< --------- 8< --------- 8< --------- 8< ---------
#+TITLE: test title

* First heading
  - Turn this into a long sentence to see the bug.

--------- 8< --------- 8< --------- 8< --------- 8< --------- 8< ---------

If you extend the sentence by adding only words and spaces, when it
wraps, indentation is broken and a # appears from nowhere:

--------- 8< --------- 8< --------- 8< --------- 8< --------- 8< ---------
#+TITLE: test title

* First heading
  - Turn this into a long sentence to see the bug.  Or you can start a
#new sentence; either way you get that strange #-prefixed outdentation.
--------- 8< --------- 8< --------- 8< --------- 8< --------- 8< ---------

The odd thing is that if there is nothing in the buffer after the
point when you start (not even a newline) then the bug vanishes.

Reproduced with a recent git clone claiming to be 5.20, and also with
5.17.  Thanks!

Re: auto-fill bug

[Carsten Dominik]

[-- Attachment #1.1: Type: text/plain, Size: 1567 bytes --]

Probably you have set the value of comment-start to "#" somewhere in  
your
customization?  There is something wring with the line wrapping in
combination with this setting, I have not yet understood what.  So for  
now,
leave comment-start alone.

- Carsten

On Feb 11, 2008, at 1:32 PM, Adam Spiers wrote:

> I just found some strange behaviour with auto-fill mode on:
>
> --------- 8< --------- 8< --------- 8< --------- 8< --------- 8<  
> ---------
> #+TITLE: test title
>
> * First heading
>  - Turn this into a long sentence to see the bug.
>
> --------- 8< --------- 8< --------- 8< --------- 8< --------- 8<  
> ---------
>
> If you extend the sentence by adding only words and spaces, when it
> wraps, indentation is broken and a # appears from nowhere:
>
> --------- 8< --------- 8< --------- 8< --------- 8< --------- 8<  
> ---------
> #+TITLE: test title
>
> * First heading
>  - Turn this into a long sentence to see the bug.  Or you can start a
> #new sentence; either way you get that strange #-prefixed  
> outdentation.
> --------- 8< --------- 8< --------- 8< --------- 8< --------- 8<  
> ---------
>
> The odd thing is that if there is nothing in the buffer after the
> point when you start (not even a newline) then the bug vanishes.
>
> Reproduced with a recent git clone claiming to be 5.20, and also with
> 5.17.  Thanks!
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode


[-- Attachment #1.2: Type: text/html, Size: 2048 bytes --]

[-- Attachment #2: Type: text/plain, Size: 204 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: auto-fill bug

[Adam Spiers]

Carsten Dominik (dominik@science.uva.nl) wrote:
> Probably you have set the value of comment-start to "#" somewhere in
> your customization?  There is something wring with the line wrapping
> in combination with this setting, I have not yet understood what.
> So for now, leave comment-start alone.

Actually it's set to "> ", which is even more puzzling ... :-/

Re: auto-fill bug

[Jonathan Moore]

Adam Spiers <orgmode <at> adamspiers.org> writes:

> 
> Carsten Dominik (dominik <at> science.uva.nl) wrote:
> > Probably you have set the value of comment-start to "#" somewhere in
> > your customization?  There is something wring with the line wrapping
> > in combination with this setting, I have not yet understood what.
> > So for now, leave comment-start alone.
> 
> Actually it's set to "> ", which is even more puzzling ... :-/
> 

You'll have problems if comment-start is set as a global variable in some other
mode.  If so, edit the other mode to make it a local variable before setting it.

Otherwise org's auto-filling will try to work with the comment syntax, even if
you don't set comment-start in it (there is also a call to modify-syntax-entry)

Regards
Jon

auto-fill bug

[Samuel Wales]

I expect "I can't reproduce this" but wanted to document it.

Often when I press SPC beyond fill-column, the new Org filling mechanism
inserts " " at bol.  fill-paragraph works fine.

A buggy fill-prefix is returned by org-adaptive-fill-function on this line:

		    ((looking-at "[ \t]*") (match-string 0))

That's all I know.

Samuel

-- 
The Kafka Pandemic: http://thekafkapandemic.blogspot.com

Re: auto-fill bug

[Nicolas Goaziou]

Hello,

Samuel Wales <samologist@gmail.com> writes:

> I expect "I can't reproduce this" but wanted to document it.

#+BEGIN_SRC emacs-lisp
(defun ngz-handle-bug-reports ()
  (when (save-excursion (message-goto-to)
                        (beginning-of-line)
                        (looking-at ".*Samuel Wales"))
    (insert "I can't reproduce this\n")
    (message-send-and-exit)))
#+END_SRC

> Often when I press SPC beyond fill-column, the new Org filling mechanism
> inserts " " at bol.  fill-paragraph works fine.
>
> A buggy fill-prefix is returned by org-adaptive-fill-function on this line:
>
> 		    ((looking-at "[ \t]*") (match-string 0))
>
> That's all I know.

Indeed. This regexp is obviously wrong. I've pushed a fix. Hopefully, it
should solve the problem at hand. Pleas tell me if it doesn't.

Thank you for the report.


Regards,

-- 
Nicolas Goaziou