From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Some projects
Date: Tue, 27 Oct 2015 20:23:27 +0100 [thread overview]
Message-ID: <87io5s5d5c.fsf@gmx.us> (raw)
In-Reply-To: 877fm8kusi.fsf@ericabrahamsen.net
Eric Abrahamsen <eric@ericabrahamsen.net> 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
next prev parent reply other threads:[~2015-10-27 19:23 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-25 13:08 Some projects Nicolas Goaziou
2015-10-25 14:43 ` Marcin Borkowski
2015-10-25 16:11 ` Nicolas Goaziou
2015-10-25 15:45 ` Eric S Fraga
2015-10-25 16:16 ` Nicolas Goaziou
2015-10-25 16:18 ` Marcin Borkowski
2015-10-25 16:37 ` Nicolas Goaziou
2015-10-25 18:13 ` Marcin Borkowski
2015-10-25 18:24 ` Nicolas Goaziou
2015-10-25 17:57 ` Thomas S. Dye
2015-10-25 18:00 ` Fabrice Popineau
2015-10-25 18:12 ` Nicolas Goaziou
2015-10-25 18:22 ` Eric S Fraga
2015-10-25 19:12 ` Marcin Borkowski
2015-10-25 19:11 ` Marcin Borkowski
2015-10-25 21:18 ` Anders Johansson
2015-10-25 21:29 ` Anders Johansson
2015-10-25 19:33 ` Thomas S. Dye
2015-10-25 20:00 ` Nicolas Goaziou
2015-10-25 20:17 ` Thomas S. Dye
2015-10-25 20:03 ` Nicolas Goaziou
2015-10-25 19:02 ` Rasmus
2015-10-25 19:20 ` Marcin Borkowski
2015-10-26 2:23 ` Matt Price
2015-10-25 20:24 ` Samuel Wales
2015-10-25 20:25 ` Samuel Wales
2015-10-25 23:03 ` Aaron Ecay
2015-10-26 8:13 ` Marcin Borkowski
2015-10-26 9:20 ` Rasmus
2015-10-26 16:39 ` Richard Lawrence
2015-10-26 18:17 ` Nicolas Goaziou
2015-10-26 22:23 ` Richard Lawrence
2015-10-27 0:03 ` Matt Price
2015-10-27 12:01 ` Aaron Ecay
2015-10-27 12:34 ` Rasmus
2015-10-27 13:03 ` Aaron Ecay
2015-10-27 13:51 ` Rasmus
2015-10-28 1:05 ` Matt Price
2015-10-28 3:28 ` Aldric Giacomoni
2015-10-28 3:31 ` Matt Lundin
2015-10-28 14:36 ` Matt Price
2015-10-28 15:31 ` Matt Price
2015-10-28 1:05 ` Matt Price
2015-10-27 13:19 ` Rainer M Krug
2015-10-27 13:42 ` Rasmus
2015-10-27 14:49 ` Ista Zahn
2015-10-27 15:09 ` Rasmus Pank Roulund
2015-10-27 15:25 ` Ista Zahn
2015-10-27 15:36 ` Rainer M Krug
2015-10-28 2:52 ` Matt Lundin
2015-10-27 13:22 ` Richard Lawrence
2015-10-28 1:57 ` Matt Lundin
2015-10-28 8:56 ` Rasmus
2015-10-28 9:07 ` Rasmus
2015-10-26 17:20 ` Eric Abrahamsen
2015-10-27 8:30 ` Nicolas Goaziou
2015-10-27 18:53 ` Eric Abrahamsen
2015-10-27 19:23 ` Rasmus [this message]
2015-10-27 20:28 ` Eric Abrahamsen
2015-10-27 20:01 ` Marcin Borkowski
2015-10-27 21:53 ` Nicolas Goaziou
2015-10-26 18:20 ` Kaushal Modi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87io5s5d5c.fsf@gmx.us \
--to=rasmus@gmx.us \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).