From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: Re: Some projects Date: Tue, 27 Oct 2015 20:23:27 +0100 Message-ID: <87io5s5d5c.fsf@gmx.us> References: <87wpub9jts.fsf@nicolasgoaziou.fr> <87lhap5yxx.fsf@ericabrahamsen.net> <877fm8d883.fsf@nicolasgoaziou.fr> <877fm8kusi.fsf@ericabrahamsen.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41864) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zr9qN-0002Z2-Cy for emacs-orgmode@gnu.org; Tue, 27 Oct 2015 15:23:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zr9qI-0000pp-E5 for emacs-orgmode@gnu.org; Tue, 27 Oct 2015 15:23:39 -0400 Received: from plane.gmane.org ([80.91.229.3]:47730) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zr9qI-0000pT-7q for emacs-orgmode@gnu.org; Tue, 27 Oct 2015 15:23:34 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Zr9qH-0005WH-0c for emacs-orgmode@gnu.org; Tue, 27 Oct 2015 20:23:33 +0100 Received: from 46.166.188.210 ([46.166.188.210]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 27 Oct 2015 20:23:32 +0100 Received: from rasmus by 46.166.188.210 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 27 Oct 2015 20:23:32 +0100 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 Eric Abrahamsen writes: > Right, I'd forgotten the distinction. I really only use orgstruct for > plain/numbered list editing (and I guess the occasional table), and > filling/indentation is pretty key there. AFAIK, this doesn't work in commented lines (e.g., when using orgstruct with init.el). >> I think OrgStruct may be redefined as an outline minor mode with Org >> bindings. This is very different from Org. Even indentation and filling >> should be new functions since Org's recognizes context that doesn't make >> sense in OrgStruct. > > Would that mean that lists and tables wouldn't be supported? ATM tables are supported via orgstruct++-mode, though at list basic list support is provided by orgstruct-mode. > The unfortunate thing about tabulated list mode, which I otherwise > really like, isn't able to show multi-line list items. That really > crimps its usefulness in showing footnotes and annotations, since you > can only see the first line. Bummer. Did you open a bug for this? >>> These new features aside, is there any need to do any fundamental >>> refactoring? I mostly mean altering existing Org libraries to use the >>> element framework, stuff like that... >> >> Of course. Refactoring (e.g., replacing `setq' with `let'), adding code >> comments, tests, using Element where applicable is always good. > > Okay. I thought there might be some big chunk of Org that needed to be > shifted over on top of elements. There’s plenty of stuff to refactor in org.el, org-agenda.el etc. Rasmus -- However beautiful the theory, you should occasionally look at the evidence