From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Wales Subject: Re: bugs in commenting and filling Date: Thu, 30 Aug 2012 19:01:34 -0700 Message-ID: References: <87a9xfqlzu.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([208.118.235.92]:58503) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T7GYD-0007Qx-7F for emacs-orgmode@gnu.org; Thu, 30 Aug 2012 22:01:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T7GYC-0000fJ-5u for emacs-orgmode@gnu.org; Thu, 30 Aug 2012 22:01:37 -0400 Received: from mail-ob0-f169.google.com ([209.85.214.169]:45664) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T7GYC-0000fA-1r for emacs-orgmode@gnu.org; Thu, 30 Aug 2012 22:01:36 -0400 Received: by obhx4 with SMTP id x4so5246108obh.0 for ; Thu, 30 Aug 2012 19:01:35 -0700 (PDT) In-Reply-To: <87a9xfqlzu.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nicolas Goaziou Cc: emacs-orgmode@gnu.org On 8/28/12, Nicolas Goaziou wrote: >> #bug 4: this paragraph now gets exported in HTML subtree >> #export, which will likely surprise many people who formerly >> #used "#" comments instead of "# " comments and don't >> #carefully check all output. they might >> #even publish private information automatically without >> #realizing it using old files that they forgot or did not >> #know to convert. > > This has been announced in 7.9 changes. As a user, what is the best way in both the old and new exporters to remove #[^+] lines on export? Flush lines in one of the hooks? Or is there a setting? Or error if there are any such lines in the exported subtree. (I always export subtrees.) Is this possible? >> #bug 5: filling this paragraph with "===" on the following >> #line will fill the ===, unlike the rest of emacs with >> #filladapt turned ON. we are supposed to not use filladapt >> #with org. therefore, how do you emulate the filladapt >> #behavior so that there is consistency between emacs and >> #org? > > I don't know filladapt.el. I've done my homework, though, and looked at > the file. > > If you want to use filladapt.el, you'll have to tweak > `filladapt-token-*' variables. If you come up with a working setup, > please put it on org-hacks.org as some users may appreciate it. > > For example, `cc-mode' does it in `c-setup-filladapt' function. filladapt worked as it does in the rest of Emacs until pretty recently, but it stopped working (error) when Org changed filling. This bug refers to how Org without filladapt works. Are you suggesting getting it to work again, then fixing this bug? My concern is that further changes in Org might make it not work again. The alternative is to make the Org behavior work as it used to with filladapt. > I hope it is clearer now. Yes, thanks for explaining that it is for comment and verse blocks. > Thanks for the detailed report. Thanks for addressing the bugs. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com