emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: suvayu ali <fatkasuvayu+linux@gmail.com>
To: Luis Anaya <papoanaya@hotmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Exporting to groff, now in org-export.el ...
Date: Tue, 10 Jul 2012 02:21:40 +0200	[thread overview]
Message-ID: <CAMXnza3ZYfxYS+QrMeVwfjmbrNiCt4aW0tc2ArvJAq=+h22exw@mail.gmail.com> (raw)
In-Reply-To: <BLU0-SMTP1937905D4C6BAF3B5814411B7D20@phx.gbl>

Hey Luis,

Looks good,

On Tue, Jul 10, 2012 at 2:00 AM, Luis Anaya <papoanaya@hotmail.com> wrote:
>
> I had to read on how to put colors in groff, at least I learned
> something new today :).
>
> Colorized version:
> Source: http://ppl.ug/LN7rEdf2yS4/
> PDF Output: http://ppl.ug/wlA1QvIDNSk/
>
> You'll notice that DUMMY refers to a #+begin_src dummy, this will
> default to black and white in constant width. This will happen if the
> language is not in the list of language that is stored in
> org-e-groff-listings-langs.
>
> Being that GNU source highlight allows for the creation of new
> language colorization schemes. This variable will need to be updated
> accordingly when a new language is added in source highlight to get it
> colorized/highlighted.
>

Does that mean a user can add any new language like this with her/his
definitions in their personal setup? If that is possible it would be
a really flexible setup.

> Otherwise, it will default to courier, black and white.

The defaults look pretty good for a fallback. :)

Sorry to nitpick, but I was wondering if it would be possible to put
some regular text in your example before or after the source blocks. It
would be good to see whether they stand out well when surrounded by
normal text.

BTW, great work. :)

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.

  reply	other threads:[~2012-07-10  0:22 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-26  3:36 Exporting to groff Luis Anaya
2012-06-26 11:33 ` Nick Dokos
2012-06-26 14:09   ` Luis Anaya
2012-06-26 14:55     ` Nicolas Goaziou
2012-06-29 23:58       ` Exporting to groff, now in org-export.el Luis Anaya
2012-06-30  6:42         ` Nicolas Goaziou
2012-06-30 11:56           ` Nicolas Goaziou
2012-07-03  1:18             ` Luis Anaya
2012-07-03  9:51               ` Nicolas Goaziou
2012-07-05 22:46                 ` Luis Anaya
2012-07-06  7:14                   ` Nicolas Goaziou
2012-07-07 14:25                     ` #+CAPTION: Not being protected when they are used with #+begin_src Luis Anaya
2012-07-07 17:15                       ` Eric Schulte
2012-07-07 19:00                         ` Luis Anaya
2012-07-07 19:01                           ` Nicolas Goaziou
2012-07-07 19:33                             ` Luis Anaya
2012-07-07 20:28                     ` Exporting to groff, now in org-export.el Luis Anaya
2012-07-07 20:31                     ` Luis Anaya
2012-07-07 22:59                       ` suvayu ali
2012-07-08  1:49                         ` Luis Anaya
2012-07-08  1:56                           ` suvayu ali
2012-07-08 13:14                             ` Luis Anaya
2012-07-08 14:07                               ` Suvayu Ali
2012-07-09  0:29                                 ` Luis Anaya
2012-07-09 20:32                                 ` Luis Anaya
2012-07-09 21:23                                   ` suvayu ali
2012-07-09 21:55                                     ` Luis Anaya
2012-07-09 22:01                                       ` suvayu ali
2012-07-10  0:00                                         ` Luis Anaya
2012-07-10  0:21                                           ` suvayu ali [this message]
2012-07-10  1:09                                             ` Luis Anaya
2012-07-10  1:20                                               ` suvayu ali
2012-07-10 13:30                                                 ` Luis Anaya
2012-06-30 22:36           ` Luis Anaya
2012-07-13 18:51           ` Luis Anaya

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='CAMXnza3ZYfxYS+QrMeVwfjmbrNiCt4aW0tc2ArvJAq=+h22exw@mail.gmail.com' \
    --to=fatkasuvayu+linux@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=papoanaya@hotmail.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).