emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: emacs-orgmode@gnu.org, carsten.dominik@gmail.com
Subject: Re: Enriched/Org is a colorful Org
Date: Wed, 10 Apr 2013 20:13:16 +0300	[thread overview]
Message-ID: <834nfeb977.fsf@gnu.org> (raw)
In-Reply-To: <871uaiibel.fsf@gmail.com>

> From: Jambunathan K <kjambunathan@gmail.com>
> Cc: Carsten Dominik <carsten.dominik@gmail.com>,  emacs-orgmode@gnu.org
> Date: Wed, 10 Apr 2013 22:13:46 +0530
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > I beg the Org developers to please be very careful when introducing
> > expensive display features such as overlays into Org.  Org already
> > puts the Emacs display engine to its limits in many of its popular
> > features; adding overlays to this mess might be too much.
> 
> We shouldn't be afraid of building a prototype or release the feature
> with a warning "you are on your own".

Fear has nothing to do with this.  Good software design takes into
consideration the particulars and the limitation of the
infrastructure, and tries to avoid limitations and weak spots in that
infrastructure.  Building a house on shaky ground is silly; at best it
is waste of effort.

> >From Org side of things, it is the rigidity of Org syntax wrt emphasis
> etc.  From user side of things, an ability to color code his notes (and
> possibly create an exported document that retains those highlights.)

I meant technical details.  The above is too high-level to be useful.

> The intention is to really keep the discussion moving and see what comes
> out of it.

My intent was to advise people not to go in directions that can hardly
be fruitful.  Of course, if they want to...

  reply	other threads:[~2013-04-10 17:13 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10  4:02 Enriched/Org is a colorful Org Jambunathan K
2013-04-10  9:54 ` Suvayu Ali
2013-04-10 10:16   ` Carsten Dominik
2013-04-10 10:39     ` Torsten Wagner
2013-04-10 10:48     ` Suvayu Ali
2013-04-10 10:53       ` Carsten Dominik
2013-04-10 11:20         ` Sebastien Vauban
2013-04-10 11:26           ` Carsten Dominik
2013-04-10 12:15           ` Jambunathan K
2013-04-10 11:57     ` Jambunathan K
2013-04-10 16:21     ` Eli Zaretskii
2013-04-10 16:43       ` Jambunathan K
2013-04-10 17:13         ` Eli Zaretskii [this message]
2013-04-10 19:58       ` Carsten Dominik
2013-04-10 20:16         ` Sebastien Vauban
2013-04-11  2:58           ` Carsten Dominik
2013-04-11 17:30             ` Eli Zaretskii
2013-04-11 22:49               ` Carsten Dominik
2013-04-12  6:41                 ` Eli Zaretskii
2013-04-12  7:13                   ` Carsten Dominik
2013-04-12  8:31                     ` Eli Zaretskii
2013-04-12 10:56                       ` Carsten Dominik
2013-04-12 11:49                         ` Torsten Wagner
2013-04-12 13:03                           ` Eli Zaretskii
2013-04-12 18:00                             ` Suvayu Ali
2013-04-12 18:38                               ` Eli Zaretskii
2013-04-13 10:50                                 ` Suvayu Ali
2013-04-12 12:36                         ` Eli Zaretskii
2013-04-13 12:24                           ` Sean O'Halpin
2013-04-13 14:38                             ` Jambunathan K
2013-04-13 15:01                             ` Eli Zaretskii
2013-04-12  8:35                     ` Bastien
2013-04-12 14:45                       ` François Pinard
2013-04-18 20:37                         ` Samuel Wales
2013-04-11 17:27         ` Eli Zaretskii
2013-04-11 22:46           ` Carsten Dominik
2013-04-10 12:12   ` Jambunathan K

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=834nfeb977.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=kjambunathan@gmail.com \
    /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).