emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Guido Van Hoecke <guivho@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: Rendering of source code on worg
Date: Fri, 24 May 2013 19:47:00 +0200	[thread overview]
Message-ID: <m2fvxc2ru3.fsf@gmail.com> (raw)
In-Reply-To: <871u8w8ew5.fsf@bzg.ath.cx> (Bastien's message of "Fri, 24 May 2013 19:30:02 +0200")

Hi Bastien,

Bastien <bzg@gnu.org> writes:

> Hi Guido,
>
> Guido Van Hoecke <guivho@gmail.com> writes:
>
>> I think that the default rendering of source code on the worg side was
>> closely resmbling the default rendering on emacs.
>>
>> I have the impression that somehow this is no longer the case, as
>> visible a.o. at
>> http://orgmode.org/worg/org-configs/org-config-examples.html
>>
>> Is this a deliberate choice?
>
> The .emacs.el on orgmode.org contains:
>
>   (set-face-foreground 'font-lock-keyword-face "DeepSkyBlue1")
>   (set-face-foreground 'font-lock-string-face "Goldenrod")
>
> This is used when publishing Worg files on the server.
>
> If you can find better colors, please submit some.

I never intended to comment nor judge the specific colors used.

I was under the impression that the elisp fragments on the website used
to have exactly the same font and faces as in stock emacs elisp
buffers. Apparently this is not the case, and I still don't know where I
got that wrong idea.

Anyhow, sorry for the noise,


Guido

--
The problems of business administration in general, and database management in
particular are much too difficult for people that think in IBMese, compounded
with sloppy English.
		-- Edsger W. Dijkstra

  reply	other threads:[~2013-05-24 17:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24  9:00 Rendering of source code on worg Guido Van Hoecke
2013-05-24 17:30 ` Bastien
2013-05-24 17:47   ` Guido Van Hoecke [this message]
2013-06-04 10:15     ` 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=m2fvxc2ru3.fsf@gmail.com \
    --to=guivho@gmail.com \
    --cc=bzg@gnu.org \
    --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).