From: Sharon Kimble <boudiccas@skimble.plus.com>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: "emacs-orgmode@gnu.org" <Emacs-orgmode@gnu.org>
Subject: Re: double underlines and external references
Date: Mon, 18 Dec 2017 21:56:14 +0000 [thread overview]
Message-ID: <87po7bzon5.fsf@skimble.plus.com> (raw)
In-Reply-To: <CAJ51ETqUO-=mGJ6Xi-+Q6Lg1QN8NEyM76J_iHoUywwiKkwHZMA@mail.gmail.com> (John Kitchin's message of "Wed, 13 Dec 2017 14:19:53 -0800")
[-- Attachment #1: Type: text/plain, Size: 4545 bytes --]
John Kitchin <jkitchin@andrew.cmu.edu> writes:
Thanks for replying John.
> I see, if it is just export you can still use a link with custom exporters for internal and external recipes. eg: [[irec: some recipe label]] might export to \uline{some recipe label} and [[erec:some other recipe]] might export to \
> uuline{some other recipe}, and you would use the ulem latex package to get those commands.
\uuline is working very nicely, and I've set it up through a yasnippet
--8<---------------cut here---------------start------------->8---
# -*- mode: snippet -*-
# name: double-underline
# key: ulx
# --
\uuline{
--8<---------------cut here---------------end--------------->8---
Thanks
Sharon.
> The colors I was referring to were for your benefit in org-mode to make it easy to see which kind of link it is.
>
> Another alternative is a macro:
>
> #+MACRO: irec \uline{$1}
> #+MACRO: erec \uuline{$1}
> #+LATEX_HEADER: \usepackage{ulem}
> {{{irec(some label)}}} and {{{erec(some other label)}}}
>
> This exports to: \uline{some label} and \uuline{some other label}
>
> John
>
> -----------------------------------
> Professor John Kitchin
> Doherty Hall A207F
> Department of Chemical Engineering
> Carnegie Mellon University
> Pittsburgh, PA 15213
> 412-268-7803
> @johnkitchin
> http://kitchingroup.cheme.cmu.edu
>
> On Wed, Dec 13, 2017 at 10:05 AM, Sharon Kimble <boudiccas@skimble.plus.com> wrote:
>
> John Kitchin <jkitchin@andrew.cmu.edu> writes:
>
> > You could just use regular links for this. You could setup a face function that changes the color depending on it being internal or external, or you could make separate links for them. See
> > http://kitchingroup.cheme.cmu.edu/blog/2016/11/04/New-link-features-in-org-9/ for many examples of what kinds of things can be done.
> >
> > John
>
> Thanks for replying John.
>
> I don't think I was quite as explicit as I should've been. I'm exporting
> my org-mode documents into latex ones, which are then building a PDF,
> which can then be printed in black and white (with no other colours
> being allowed), with the ultimate aim of it being professionally printed
> as books.
>
> Hence my need for both, double and single line, underlines.
>
> But I'm also open to any other way of finding some other way of showing
> the different links, but I can only use either black or white colours.
>
> Thanks
> Sharon.
>
> > -----------------------------------
> > Professor John Kitchin
> > Doherty Hall A207F
> > Department of Chemical Engineering
> > Carnegie Mellon University
> > Pittsburgh, PA 15213
> > 412-268-7803
> > @johnkitchin
> > http://kitchingroup.cheme.cmu.edu
> >
> > On Wed, Dec 13, 2017 at 6:56 AM, Sharon Kimble <boudiccas@skimble.plus.com> wrote:
> >
> > For my current series of books that I'm writing in org-mode which is
> > being exported to latex, I need to differentiate between recipes in the
> > current working file, and to recipes in an external file. This is in a
> > series of books all containing recipes. So what I'm looking for is the
> > ability to use a single underline for internal, and a double underline
> > for external. I can do a single underline easily in org-mode, but I'm
> > having problems with a double underline.
> >
> > But is it the best method, using single and double underlines? Can
> > anyone suggest some other ways of doing it, please? Like, for instance,
> > can I have a reference to a particular section in another file?
> >
> > Thanks
> > Sharon
> > --
> > A taste of linux = http://www.sharons.org.uk
> > TGmeds = http://www.tgmeds.org.uk
> > DrugFacts = https://www.drugfacts.org.uk
> > Debian 9.3, fluxbox 1.3.5-2, emacs 25.3.2, org-mode 9.1.4-2
> >
>
> --
> A taste of linux = http://www.sharons.org.uk
> TGmeds = http://www.tgmeds.org.uk
> DrugFacts = https://www.drugfacts.org.uk
> Debian 9.3, fluxbox 1.3.5-2, emacs 25.3.2, org-mode 9.1.4-2
>
--
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
DrugFacts = https://www.drugfacts.org.uk
Debian 9.3, fluxbox 1.3.5-2, emacs 25.3.2, org-mode 9.1.4-2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2017-12-18 21:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 14:56 double underlines and external references Sharon Kimble
2017-12-13 15:27 ` John Kitchin
2017-12-13 18:05 ` Sharon Kimble
2017-12-13 22:19 ` John Kitchin
2017-12-18 21:56 ` Sharon Kimble [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=87po7bzon5.fsf@skimble.plus.com \
--to=boudiccas@skimble.plus.com \
--cc=Emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
/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).