From: Samuel Wales <samologist@gmail.com>
To: Kevin Rodgers <kevin.d.rodgers@gmail.com>
Cc: help-gnu-emacs@gnu.org, emacs-orgmode@gnu.org
Subject: Re: desirability of boxquote-style snippets for helping new users
Date: Fri, 18 Aug 2023 13:46:56 -0700 [thread overview]
Message-ID: <CAJcAo8sZuCSzwmAN0piseO6yfehq=cTKrHgZQmNkytfrruUGZA@mail.gmail.com> (raw)
In-Reply-To: <gkp358$o99$2@ger.gmane.org>
On 1/15/09, Kevin Rodgers <kevin.d.rodgers@gmail.com> wrote:
>> 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?
>
> ,----[ C-h f boxquote-unbox RET ]
> | boxquote-unbox is an interactive compiled Lisp function in `boxquote.el'.
> | (boxquote-unbox)
> |
> | Remove the boxquote that contains `point'.
> |
> | [back]
> `----
thanks for your suggestion.
as i said, i am suggesting that the prefixed lines should never be
prefixed in the first place. i don't think it adds enough to outweigh
the extra keystrokes, rectangle, boxquote package, etc. i don't think
all newcomers will know what to do.
imho, above and below quoting is a preferable default convention.
exceptions are few and can be optional.
next prev parent reply other threads:[~2023-08-18 20:48 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
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 [this message]
2009-01-16 9:56 ` Tassilo Horn
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='CAJcAo8sZuCSzwmAN0piseO6yfehq=cTKrHgZQmNkytfrruUGZA@mail.gmail.com' \
--to=samologist@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=kevin.d.rodgers@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 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).