From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Worg publishing broken?
Date: Sat, 19 Feb 2011 15:04:32 +0100 [thread overview]
Message-ID: <80zkpsjf2n.fsf@missioncriticalit.com> (raw)
In-Reply-To: <87pqqosucm.fsf-mXXj517/zsQ@public.gmane.org> (Bastien's message of "Sat, 19 Feb 2011 02:09:45 +0100")
Hi Jambunathan and Bastien,
Bastien wrote:
> Jambunathan K <kjambunathan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>>> 1) Used "shell" instead of "sh" for the source block mode. Fixed by
>>> commit e4ed828.
>>
>> If known languages are treated as "keywords" in #+begin_src context and
>> fontified appropriately there would be enough visual feedback so that a
>> user's `eye memory' could catch that something is amiss.
>
> Good idea -- I need time to explore org-src.el and I'm pretty sure Eric and
> Sebastien will be faster than me :)
What I can say is that this feature is scheduled (well, not really) on my
private task list for Org. Not only languages, but as well highlight of all
other keywords such as `:vars', `:exports' and the like.
Best regards,
Seb
--
Sébastien Vauban
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2011-02-19 14:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 16:17 Worg publishing broken? Carsten Dominik
2011-02-16 16:30 ` Bastien
2011-02-16 16:34 ` Jason Dunsmore
2011-02-16 16:41 ` Bastien
2011-02-17 16:27 ` Matt Lundin
2011-02-18 8:58 ` Bastien
2011-02-18 16:19 ` Jason Dunsmore
2011-02-18 18:05 ` Jambunathan K
2011-02-19 1:09 ` Bastien
[not found] ` <87pqqosucm.fsf-mXXj517/zsQ@public.gmane.org>
2011-02-19 14:04 ` Sébastien Vauban [this message]
2011-02-22 11:53 ` Bastien
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=80zkpsjf2n.fsf@missioncriticalit.com \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).