From: Matthew Lundin <firstname.lastname@example.org>
To: Samuel Wales <email@example.com>
Cc: firstname.lastname@example.org, email@example.com
Subject: Re: desirability of boxquote-style snippets for helping new users
Date: Thu, 15 Jan 2009 20:13:31 -0600 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Samuel Wales's message of "Thu\, 15 Jan 2009 18\:41\:31 -0700")
"Samuel Wales" <firstname.lastname@example.org> writes:
> I have noticed more people using boxquote and similar ways of setting
> off code. This makes it pretty and makes it stand out, both of which
> are good things.
> However, most prefix every line. For example, boxquote by default uses "|".
> While an experienced user can figure out rectangle commands or write a
> command to unpack the quote, new users and users who can't type much
> might skip using the code to avoid having to do that. And a very new
> user could actually stick the whole thing in .emacs and wonder why it
> doesn't work. It adds to the burden of fixing a problem or meeting a
> need in emacs without providing much benefit. Even a few keystrokes
> can do that.
> Perhaps quotes of code, in all packages like boxquote, could by
> default get fancy only on the lines precediing and following.
> What do you think?
I hadn't thought of that. I started using boxquote because I was
looking for an easier way to set off code. But if it's a nuisance or a
problem to new users, then I'd be happy to modify the variable
Something like this perhaps?
(setq boxquote-side " ")
What do others think? Is this readable enough?
The only downside is that the cursor has to be on the beginning or
ending line for commands such as boxquote-unbox or boxquote-yank or
boxquote-narrow-to-boxquote to work.
> For personal gain, myalgic encephalomyelitis denialists are knowingly
> causing massive suffering and 25-years-early death by grossly
> corrupting science.
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
next prev parent reply other threads:[~2009-01-16 2:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 1:41 desirability of boxquote-style snippets for helping new users Samuel Wales
2009-01-16 2:13 ` Matthew Lundin [this message]
2009-01-16 2:32 ` Austin Frank
2009-01-16 3:34 ` Matthew Lundin
2009-01-16 4:41 ` Kevin Rodgers
2023-08-18 20:46 ` Samuel Wales
2009-01-16 9:56 ` Tassilo Horn
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).