From: Peter Salazar <cycleofsong@gmail.com>
To: John Hendy <jw.hendy@gmail.com>
Cc: org-mode <emacs-orgmode@gnu.org>
Subject: Re: block quotes in prose?
Date: Mon, 4 Feb 2013 23:10:47 -0500 [thread overview]
Message-ID: <CAE+_6TyUrs4o9Myjh2T4NFyEyPK+QocKsr0+MZLHbPB5Xo07yA@mail.gmail.com> (raw)
In-Reply-To: <CA+M2ft8Z+4=2z41+m2SZaMM=G0pmvPQq3B3XRGyRxPwo=nGimA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3192 bytes --]
I think an easy workaround would be to define block quotes as code blocks
instead.
putting the ":" as a prefix before a paragraph automatically fontifies it
and places it in another color.
This allows me to work in org-mode with visual highlighting of block quotes
as desired.
Now the question is: How do I make org-mode recognize the ">" prefix as a
demarcator of a code block, so that my document remains readable as
Markdown?
Thanks!
On Wed, Jan 23, 2013 at 12:03 AM, John Hendy <jw.hendy@gmail.com> wrote:
> On Tue, Jan 22, 2013 at 6:13 PM, Peter Salazar <cycleofsong@gmail.com>
> wrote:
> > 1. What's the best way to demarcate block quotes in org-mode? I'd like a
> way
> > to demarcate them that makes it visually clear at a glance that it's a
> block
> > quote and not regular text.
> >
> > I would prefer not to have to put them inside #+BEGIN_QUOTE and
> #+END_QUOTE
> > references, because I'd rather not have any content in my buffer that
> > distracts me from my actual writing.
> >
> > In Markdown-Mode, for instance, I just prefix a block quote with a > and
> the
> > line automatically changes color:
> >
> > http://i.imgur.com/AUsYJ.png
> >
> > Org-mode is infinitely more powerful than Markdown-Mode, so I'd just
> like a
> > way to work with lots of prose and block quotes in org-mode that will be
> > easy and visually pleasing. I'm primarily concerned about how it appears
> in
> > the org-mode editor, not in export.
> >
>
> Looking around, at least some of this appears defined in
> /path/to/org-src/lisp/org-faces.el.
>
> I don't know enough elisp to tell you how to make Org treat ">
> text..." the same as #+begin_quote.
>
> Perhaps you could figure out where the face change is for lines like
> #+latex: and #+begin_src, as they both change the face of the text
> immediately after (no need for an #+end_ command to tell Org to go
> back to the default face). You might be able to add "^> text" to the
> list of face-sensitive regexps to look for (using ^ as symbol for
> beginning of line).
>
> ETA: after some more grepping, it looks like you could add something
> in two places:
>
> 1) org-faces.el
>
> Search the file for "defface" and make a new face. I've not done this,
> but you can definitely copy/yank some existing definitions and tweak
> to your liking.
>
> 2) org.el
>
> Find a matching fontify function to see how the fontification is done.
> They look pretty complicated... but perhaps it's possible to tweak one
> to fontify "^> text...".
>
> Perhaps the easiest would be to find a face you like and just add "^>
> text..." to the existing list of things org already fontifies with
> that style. In other words, add "^> text" regexp to the existing hunt
> for lines that start with #+ in order to get src code fontification
> applied.
>
> > 2. It would also be cool to find a way to make bulleted lists appear in a
> > different color if possible, or a workaround to simulate this.
>
> As in?
> - item 1
> - item 2
>
> I'm sure that's possible, too. Can't imagine this will become global,
> but you could surely create your own git branch if you figure out how
> or someone tells you how.
>
>
> Good luck!
> John
>
>
> >
> > Thanks!
> >
> >
>
[-- Attachment #2: Type: text/html, Size: 4152 bytes --]
next prev parent reply other threads:[~2013-02-05 4:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 0:13 block quotes in prose? Peter Salazar
2013-01-23 5:03 ` John Hendy
2013-02-05 4:10 ` Peter Salazar [this message]
2013-02-11 15:54 ` Bastien
2013-02-11 16:01 ` Sebastien Vauban
2013-02-16 20:27 ` Peter Salazar
2013-02-23 9:54 ` Bastien
2013-02-24 19:45 ` Peter Salazar
2013-01-23 12:44 ` Bastien
2013-01-24 6:36 ` Peter Salazar
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAE+_6TyUrs4o9Myjh2T4NFyEyPK+QocKsr0+MZLHbPB5Xo07yA@mail.gmail.com \
--to=cycleofsong@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jw.hendy@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.