From: "Samuel Wales" <samologist@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-plot questions
Date: Wed, 22 Oct 2008 18:14:14 -0700 [thread overview]
Message-ID: <20524da70810221814i5e04fde7w80d21177fbb0fb5f@mail.gmail.com> (raw)
In-Reply-To: <8763nkl08a.fsf@gmail.com>
On Wed, Oct 22, 2008 at 15:43, Eric Schulte <schulte.eric@gmail.com> wrote:
> I agree this isn't obvious, if you have a suggestion for improving the
> syntax please let me know.
I haven't looked into this matter, so this comment might not be
relevant, but I do have a suggestion that I had earlier written for
the *general* problem of choosing a syntax for new functionality when
you don't have obvious models to follow.
Some of the desiderata for a syntax include: consistent, easy to
parse, hard to corrupt, simple to quote, simple to escape (especially
with things like regexps that are already complicated), supports being
confident that exporting will not exhibit unexpected behavior, easier
for the user to remember without reference materials, flexible,
extensible, supports macros, nestable, pretty-printable, a published
reference standard, and print-readable (serializing). If your syntax
has those, then you're doing well.
If you don't have a model to follow (such as org or gnuplot), then
Lisp (el because this is el or cl because it's a standard that is
similar to el and meticulously speced) has usually had a lot of
thought put into its syntax. You might get a joke or two, but we know
better. :)
Again, perhaps not relevant, but maybe food for thought for future
questions about syntax.
prev parent reply other threads:[~2008-10-23 1:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 14:27 org-plot questions JBash
2008-10-22 15:35 ` Eric Schulte
2008-10-22 17:39 ` JBash
2008-10-22 22:43 ` Eric Schulte
2008-10-23 1:14 ` Samuel Wales [this message]
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=20524da70810221814i5e04fde7w80d21177fbb0fb5f@mail.gmail.com \
--to=samologist@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@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).