From: Nick Dokos <nicholas.dokos@hp.com>
To: "Filippo A. Salustri" <salustri@ryerson.ca>
Cc: Juan Pechiar <juan@pechiar.com>,
emacs-orgmode@gnu.org, nicholas.dokos@hp.com
Subject: Re: hide #+ lines?
Date: Sat, 19 Mar 2011 22:19:55 -0400 [thread overview]
Message-ID: <11112.1300587595@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Message from "Filippo A. Salustri" <salustri@ryerson.ca> of "Sat, 19 Mar 2011 21:58:33 EDT." <AANLkTik8nKkfK+RBbVpz4kdVL3+cWC+rgZWtE5ya+nH_@mail.gmail.com>
Filippo A. Salustri <salustri@ryerson.ca> wrote:
> You're right of course. Sorry about the mixup with the attribution.
There was nothing wrong with your attribution.
I was just adding some information to my previous posting about who
suggested the drawer solution, but more importantly, adding the bit
of setup needed: I think it's important to make each thread complete
or provide enough references so that future wanderers can find their
way without too much trouble.
> Nick, your previous post that mentioned org-drawers helped my hide the
> eval line. Thanks for that.
>
> As for the #+BEGIN block, my installation shows these lines in a
> rather gaudy orange, which I do find distracting.
> I found that those lines do have their own face, so I made 'em dark
> grey (my background is black). I can still see them, but it's the
> text in the block that stands out now.
>
That sounds like a good solution.
Nick
next prev parent reply other threads:[~2011-03-20 2:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 21:27 hide #+ lines? Filippo A. Salustri
2011-03-19 22:06 ` Juan Pechiar
2011-03-19 22:26 ` Nick Dokos
2011-03-19 22:38 ` Filippo A. Salustri
2011-03-20 1:42 ` Nick Dokos
2011-03-20 1:58 ` Filippo A. Salustri
2011-03-20 2:19 ` Nick Dokos [this message]
2011-03-20 14:46 ` Filippo A. Salustri
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=11112.1300587595@alphaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=juan@pechiar.com \
--cc=salustri@ryerson.ca \
/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).