From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brady Trainor Subject: Re: org-html-use-unicode-chars breaks source code blocks Date: Sun, 16 Aug 2015 11:47:55 -0700 Message-ID: References: <871tfjq7mb.fsf@gmx.us> <87zj26gart.fsf@nicolasgoaziou.fr> <87zj23h168.fsf@gmx.us> <87egjftmd4.fsf@nicolasgoaziou.fr> <87614r2wow.fsf@gmx.us> <878u9bpco0.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47032) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZR2yd-00072C-1Y for emacs-orgmode@gnu.org; Sun, 16 Aug 2015 14:48:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZR2yX-0002dD-Rj for emacs-orgmode@gnu.org; Sun, 16 Aug 2015 14:48:14 -0400 Received: from plane.gmane.org ([80.91.229.3]:49066) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZR2yX-0002ax-Kw for emacs-orgmode@gnu.org; Sun, 16 Aug 2015 14:48:09 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1ZR2yV-00029I-UG for emacs-orgmode@gnu.org; Sun, 16 Aug 2015 20:48:07 +0200 Received: from 50.245.151.59 ([50.245.151.59]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 16 Aug 2015 20:48:02 +0200 Received: from algebrat by 50.245.151.59 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 16 Aug 2015 20:48:02 +0200 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: emacs-orgmode@gnu.org Speaking of COMMENT, I had noticed some strange behavior if I have a state like COMMENTED_OUT. If I have a header like =#+TODO: TODO COMMENTED_OUT | DONE=, and cycle through state with S-, it gets pretty wonky. For now, I simply use COMMENT when I have a section I want to consider as commented out, but ideally this can behavior can be different? Always true, but I haven't been on the mailing list for a spell, so, big thanks to all who contribute to this software. Bastien Guerry writes: > Andreas Leha writes: > >> So, even if there is probably not a high risk for the COMMENT keyword to >> be dropped I just wanted to express my support for it. > > COMMENT will stay, for sure. -- Brady