From: Marcin Borkowski <mbork@mbork.pl>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>,
Emanuel Berg <embe8573@student.uu.se>
Subject: Re: How to get the ~ functionality of vi
Date: Fri, 03 Jun 2016 07:07:45 +0200 [thread overview]
Message-ID: <87h9da97xa.fsf@mbork.pl> (raw)
In-Reply-To: <CAFyQvY3NGf=NWfjtRGRusfCbhAb9KoCJJk9U0zyXnH-hfwC1PQ@mail.gmail.com>
On 2016-06-02, at 23:00, Kaushal Modi <kaushal.modi@gmail.com> wrote:
> On Thu, Jun 2, 2016 at 4:41 PM Emanuel Berg <embe8573@student.uu.se> wrote:
>
>> "Lazy"?! I think "over-engineering" is
>> the word :)
>>
>
> That's subjective to how often you use that elisp snippet.
>
>
>> What is the hang up with case, anyway? I very
>> seldom do `upcase-region' but that is it.
>
>
> As I mentioned, that's subjective. I use that function to either
> lowercase/uppercase/capitalize at least once every day (not exaggerating).
> --
FWIW, I never use upcase-region, but I use capitalize-word and
downcase-word quite often, with positive and negative arguments.
Best,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University
next prev parent reply other threads:[~2016-06-03 5:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 22:36 How to get the ~ functionality of vi Cecil Westerhof
2016-05-27 1:15 ` Emanuel Berg
2016-05-27 4:28 ` Jean-Jacques Rétorré
2016-05-27 8:54 ` Cecil Westerhof
2016-05-27 11:33 ` Thorsten Bonow
2016-05-27 19:41 ` Emanuel Berg
2016-06-02 16:14 ` Kaushal Modi
[not found] ` <mailman.703.1464884068.1216.help-gnu-emacs@gnu.org>
2016-06-02 17:15 ` Emanuel Berg
2016-06-02 17:28 ` Kaushal Modi
[not found] ` <mailman.715.1464888555.1216.help-gnu-emacs@gnu.org>
2016-06-02 20:39 ` Emanuel Berg
2016-06-02 21:00 ` Kaushal Modi
2016-06-03 5:07 ` Marcin Borkowski [this message]
[not found] ` <mailman.730.1464901264.1216.help-gnu-emacs@gnu.org>
2016-06-02 21:07 ` Emanuel Berg
2016-06-03 9:21 ` Joost Kremers
2016-06-03 10:51 ` Emanuel Berg
2016-05-27 19:37 ` Emanuel Berg
2016-05-27 19:37 ` Emanuel Berg
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h9da97xa.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=embe8573@student.uu.se \
--cc=help-gnu-emacs@gnu.org \
--cc=kaushal.modi@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.
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).