From mboxrd@z Thu Jan 1 00:00:00 1970 From: Manuel Amador Subject: Re: Re: Comments in Org-mode Date: Wed, 15 Jul 2009 10:48:52 -0700 Message-ID: <20090715174852.GE21551@laflaca.Stanford.EDU> References: <20090715000930.GC4210@laflaca.Stanford.EDU> <20090715004451.GB21248@thinkpad.adamsinfoserv.com> <877hya7nnf.fsf@kassiopeya.MSHEIMNETZ> <927aeeaf0907142045o10d4a246p95c4f6b979921449@mail.gmail.com> <20090715045229.GA1761@thinkpad.adamsinfoserv.com> <20524da70907142206m1550a830p21afb1cabc9a2593@mail.gmail.com> <927aeeaf0907142223q726152e6kbc95c0d2c777e2d4@mail.gmail.com> <877hyaqajv.fsf@fastmail.fm> <87iqhtq341.fsf@kassiopeya.MSHEIMNETZ> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MR8bJ-0002ps-R0 for emacs-orgmode@gnu.org; Wed, 15 Jul 2009 13:49:05 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MR8bF-0002nl-8m for emacs-orgmode@gnu.org; Wed, 15 Jul 2009 13:49:05 -0400 Received: from [199.232.76.173] (port=46152 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MR8bF-0002nT-30 for emacs-orgmode@gnu.org; Wed, 15 Jul 2009 13:49:01 -0400 Received: from mail-bw0-f219.google.com ([209.85.218.219]:46155) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MR8bE-0000sX-Ef for emacs-orgmode@gnu.org; Wed, 15 Jul 2009 13:49:00 -0400 Received: by bwz19 with SMTP id 19so2044268bwz.42 for ; Wed, 15 Jul 2009 10:48:59 -0700 (PDT) Content-Disposition: inline In-Reply-To: <87iqhtq341.fsf@kassiopeya.MSHEIMNETZ> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Sebastian Rose Cc: emacs-orgmode@gnu.org Sebastian, The proposed fix by Samuel did seem to correct this problem for me. This is what I added to my .emacs file: (require 'filladapt) ;; fixes problems with autofill in orgmode (if (featurep 'filladapt) (filladapt-mode 1)) (setq filladapt-token-table '( ;; this must be first ("^" beginning-of-line) ;; Included text in news or mail replies (">+" citation->) ;; Included text generated by SUPERCITE. We can't hope to match all ;; the possible variations, your mileage may vary. ("\\(\\w\\|[0-9]\\)[^'`\"< \t\n]*>[ \t]*" supercite-citation) ;; Lisp comments (";+" lisp-comment) ;; UNIX shell comments ("#+" sh-comment) ;; Postscript comments ("%+" postscript-comment) ;; C++ comments ("///*" c++-comment) ;; Texinfo comments ("@c[ \t]" texinfo-comment) ("@comment[ \t]" texinfo-comment) ;; Bullet types. ;; ;; LaTex \item ;; ("\\\\item[ \t]" bullet) ;; ;; 1. xxxxx ;; xxxxx ;; ("^[ ]+[0-9]+\\.[ \t]" bullet) ;; ;; 2.1.3 xxxxx xx x xx x ;; xxx ;; ("^[ ]+[0-9]+\\(\\.[0-9]+\\)+[ \t]" bullet) ;; ;; a. xxxxxx xx ;; xxx xxx ;; ("^[ ]+[A-Za-z]\\.[ \t]" bullet) ;; ;; 1) xxxx x xx x xx or (1) xx xx x x xx xx ;; xx xx xxxx xxx xx x x xx x ;; ("^[ ]+(?[0-9]+)[ \t]" bullet) ;; ;; a) xxxx x xx x xx or (a) xx xx x x xx xx ;; xx xx xxxx xxx xx x x xx x ;; ("^[ ]+(?[A-Za-z])[ \t]" bullet) ;; ;; 2a. xx x xxx x x xxx ;; xxx xx x xx x ;; ("^[ ]+[0-9]+[A-Za-z]\\.[ \t]" bullet) ;; ;; 1a) xxxx x xx x xx or (1a) xx xx x x xx xx ;; xx xx xxxx xxx xx x x xx x ;; ("^[ ]+(?[0-9]+[A-Za-z])[ \t]" bullet) ;; ;; - xx xxx xxxx or * xx xx x xxx xxx ;; xxx xx xx x xxx x xx x x x ;; ("^[ ]+[-~*+]+[ \t]" bullet) ;; ;; o xx xxx xxxx xx x xx xxx x xxx xx x xxx ;; xxx xx xx ;; ("^[ ]+o[ \t]" bullet) ;; don't touch ("[ \t]+" space) ("$" end-of-line) )) Manuel On Wed, Jul 15, 2009 at 07:15:42PM +0200, Sebastian Rose wrote: > Matthew Lundin writes: > > Manuel Amador writes: > > > >> I think I have found a bug (or a feature!). Sometimes when > >> writing documents I tend to comment out a line by adding a "#" > >> in the column 0. However, after doing this in a line at the > >> middle of the document, I get the following behavior: > >> > >> ------------------------------------------------------------ > >> * Random stuff > >> > >> Some initial things. > >> > >> # Then I comment this line out > >> > >> But when I keep writing a sufficiently long line such that > >> # the cursor moves to the next line, a "#" character creeps in! > >> # and will keep appearing for the remainder of the document. > >> ---------------------------------------------------------- > > > > I cannot duplicate the problem (but only partially). I experienced extra > > comment lines inserted only when there was no space between the initial > > comment line and the uncommented line, i.e.: > > > > > > # Then I comment this line out > > But when I keep writing a sufficiently long line such that > > # the cursor moves to the next line, a "#" character creeps in! > > # and will keep appearing for the remainder of the document. > > > > I did not experience extra comment lines in lines further down the text. > > > I can reproduce it with `emacs -Q' here (transient-mark-mode is t in > current emacs 23). The trick is to use `comment-region'. > > Here's the recipe: > > > sh$ emacs -Q > > C-x d ~/emacs/lisp/ext/org-mode/lisp RET > % m \.elc$ RET > L y > L y > L y > L y > L y > > ... until files are loaded successfully > > C-x C-f file.org > M-x auto-fill-mode > > > > To get the error, you must select a region: > > C-SPACE C-n C-n C-n > M-x comment-region RET # RET > > Note here: the indentation is wrong. You might want to correct this, > before going on (comment char not in first column). It doesn't change > the behavior. > > > Now type some `C-j' more text and see what happens. > > > > > The bad thing is, once it started, it never ends. No matter where text > is wrapped, you get the `#' at the start of line. > > > > > > > > Also, _no_ comment char is inserted, if add a comment by hand without a > preceding new line. To try this, you'll have to restart emacs -Q > > weoru oeori tueportpoeiurptoeiurtopueoru toeuiroeuir topewrtoeoru > toeu toe ewprou oeur poeuiopuwe rteowp ru erwoi uteo t. > # Asdfsdf - NOW ADD A LOT OF TEXT TO THIS COMMENT ... > > > > > > Sebastian