From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kaushal Modi Newsgroups: gmane.emacs.devel Subject: Re: Differences between Org-Mode and Hyperbole Date: Mon, 04 Jul 2016 13:58:29 +0000 Message-ID: References: <87h9cdmj6t.fsf@delle7240.chemeng.ucl.ac.uk> <87eg7f13re.fsf@delle7240.chemeng.ucl.ac.uk> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a113ceb94def9cd0536cfbb89 X-Trace: ger.gmane.org 1467640784 21610 80.91.229.3 (4 Jul 2016 13:59:44 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 4 Jul 2016 13:59:44 +0000 (UTC) Cc: emacs-devel@gnu.org To: rms@gnu.org, Eric S Fraga Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jul 04 15:59:44 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1bK4PX-000200-66 for ged-emacs-devel@m.gmane.org; Mon, 04 Jul 2016 15:59:43 +0200 Original-Received: from localhost ([::1]:47797 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bK4PW-0000Tq-FB for ged-emacs-devel@m.gmane.org; Mon, 04 Jul 2016 09:59:42 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35121) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bK4Ob-0000Ge-A4 for emacs-devel@gnu.org; Mon, 04 Jul 2016 09:58:46 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bK4Oa-0006hz-9x for emacs-devel@gnu.org; Mon, 04 Jul 2016 09:58:45 -0400 Original-Received: from mail-oi0-x236.google.com ([2607:f8b0:4003:c06::236]:33927) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bK4OY-0006hS-FP; Mon, 04 Jul 2016 09:58:42 -0400 Original-Received: by mail-oi0-x236.google.com with SMTP id s66so195132167oif.1; Mon, 04 Jul 2016 06:58:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+i3RIKmCB82S7SzKkJdqb73D0g8kMD2uk1SI4TAuGHQ=; b=d9hr0xbyUYalffp6uZnAhBXrXmnz6346KY4khOqNcZ04bMN6Z4Mo2TEq3/oFdBZviW q1vSFHy6WXMVYM7tROg0Gkpf5XkLQXgnwC7h8mYV6tA3vyjET6uEP+xcBkzrCsTszyJv zz/YX2IVEYSWzMW3ee+BmgTmdYXXvL38SOyZQBgeptnmagGde/gvPPGwUdrhnXVxmdCd wvvHzWRpVaGIIJdQVeTTy/iGhuz9oQ5yQwn4ZsVjhj+yZTsMPntyVh6MGp0yLIeaCgt1 uE4Pqb3eLbODu6NcWMtoOt+pzlIowp+AN6f2p+8+bmp+YWOeUXJ/OElWBJItKF8ry/YT S87g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+i3RIKmCB82S7SzKkJdqb73D0g8kMD2uk1SI4TAuGHQ=; b=VWoioncEpVkTvP442Ej5lZvTBmtL+VKHuRaVymZSC9Y04YYgm8GMM1ovbhGd30g9mr K5ZKl0Joj/KoYZA1dPstDKrEnJvVAVyCrDnrCxRbZVG7K0PQdAxOpGq352Ev5BRCkgcn wddrv+UjSBtriMoI29Lep3BojNfgvKLBk2WY9w06DCqbrHjLVrYXSbeDVqrsFw3UvUDK 0E+0Yfb9VlTSQuq/bwhaaRdAKyHZut52z1xk9H9oDOzWYKZSanwb1OALXwQB1lCDh3Er Vl5U0GHWGtHo9PYIGKgbzvpmeQ6Hw1UKcrSg/RYS4eXfB1T01TJj/7rBM3cUEZIw8OZA B2VQ== X-Gm-Message-State: ALyK8tL96kcsdBNOHReKwNcpZELzvbLtoQivNKpvv7esH4Gz14YMwLvS7W9QfniZSLDwkGh95AEgG/g+1tJuSA== X-Received: by 10.202.172.146 with SMTP id v140mr7103336oie.98.1467640721633; Mon, 04 Jul 2016 06:58:41 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:4003:c06::236 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:205132 Archived-At: --001a113ceb94def9cd0536cfbb89 Content-Type: text/plain; charset=UTF-8 On Sun, Jul 3, 2016, 6:37 PM Richard Stallman wrote: > > The usual Emacs way of selecting a command set for a specific job is > to specify a major mode. Using a line that says "TODO" as to select a > command set seems inconsistent. Why not make this a major mode? > The beauty is that only that specific line has to contain the TODO information. The whole buffer is not a TODO list. If you think along those lines, org-mode has made it possible to have different major mode like behaviors in the same buffer. A single TODO headline could have the following: - Different face for displaying and different export style based on the headline level of that TODO line. - Under those TODO headlines, you can have regular or check-list style children TODO headlines. - Some of those could have just regular paragraphs or numbered/plain/definition lists or source blocks or quotation blocks or ..... which should behave in display/export as per the org mode convention. - The TODO headlines can have a "property block" which can contain a wide range of meta properties to be used during export, tangling, etc. - They can have internal/external links, footnotes, etc. This is barely skimming everything that one can have in a single headline in the same org buffer. Unless we have a way in the core to support multiple major modes in a single buffer, we cannot break out hundreds of different properties that org mode applies on the same buffer into individual major modes. > -- -- Kaushal Modi --001a113ceb94def9cd0536cfbb89 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Sun, Jul 3, 2016, 6:37 PM Ri= chard Stallman <rms@gnu.org> wrote= :

The usual Emacs way of selecting a command set for a specific job is
to specify a major mode.=C2=A0 Using a line that says "TODO" as t= o select a
command set seems inconsistent.=C2=A0 Why not make this a major mode?

The beauty is that only that specific = line has to contain the TODO information. The whole buffer is not a TODO li= st. If you think along those lines, org-mode has made it possible to have d= ifferent major mode like behaviors in the same buffer.=C2=A0

=
A single TODO headline could have the following:
- Dif= ferent face for displaying and different export style based on the headline= level of that TODO line.
- Under those TODO headlines, you can h= ave regular or check-list style children TODO headlines.
- Some o= f those could have just regular paragraphs or numbered/plain/definition lis= ts or source blocks or quotation blocks or ..... which should behave in dis= play/export as per the org mode convention.=C2=A0
- The TODO head= lines can have a "property block" which can contain a wide range = of meta properties to be used during export, tangling, etc.
- The= y can have internal/external links, footnotes, etc.

This is barely skimming everything that one can have in a single headline= in the same org buffer. Unless we have a way in the core to support multip= le major modes in a single buffer, we cannot break out hundreds of differen= t properties that org mode applies on the same buffer into individual major= modes.=C2=A0
--

--
Kaushal Modi

--001a113ceb94def9cd0536cfbb89--