From: John Wiegley <jwiegley@gmail.com>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>, emacs-devel@gnu.org
Subject: Re: Thinking about changed buffers
Date: Sun, 03 Apr 2016 22:26:35 -0700 [thread overview]
Message-ID: <m2fuv29c6s.fsf@newartisans.com> (raw)
In-Reply-To: <m3shz254qg.fsf@gnus.org> (Lars Magne Ingebrigtsen's message of "Mon, 04 Apr 2016 07:21:11 +0200")
>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> I think it's a psychological issue. If you've accepted doing convoluted
> things for years because your favourite tool lacks obvious functionality,
> then it's quite common to feel that that should never be fixed. Because
> fixing the problem would mean accepting that you've done silly things for
> years as a work around, and the obvious fix becomes a personal insult,
> almost.
I think the first part is certainly true. I've become so used to a silly
command sequence that I see nothing wrong it; but if I had to explain it to
someone else, there would be some shame. :)
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2016-04-04 5:26 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-28 17:31 Thinking about changed buffers Lars Magne Ingebrigtsen
2016-03-28 17:56 ` Andreas Schwab
2016-03-28 18:00 ` Lars Magne Ingebrigtsen
2016-03-28 18:10 ` Andreas Schwab
2016-03-28 18:19 ` Lars Magne Ingebrigtsen
2016-03-28 18:30 ` Eli Zaretskii
2016-03-28 18:53 ` Lars Magne Ingebrigtsen
2016-03-28 18:57 ` Eli Zaretskii
2016-03-28 19:06 ` Lars Magne Ingebrigtsen
2016-03-28 19:15 ` Eli Zaretskii
2016-03-28 19:23 ` Lars Magne Ingebrigtsen
2016-03-28 19:38 ` Eli Zaretskii
2016-03-28 19:46 ` Lars Magne Ingebrigtsen
2016-03-28 20:21 ` Lars Magne Ingebrigtsen
2016-03-29 2:29 ` Eli Zaretskii
2016-03-28 18:54 ` Andreas Schwab
2016-03-28 18:22 ` Eli Zaretskii
2016-03-28 18:40 ` Lars Magne Ingebrigtsen
2016-03-28 18:49 ` Stephan Mueller
2016-03-28 19:13 ` Stefan Monnier
2016-03-28 19:20 ` Lars Magne Ingebrigtsen
2016-03-28 20:13 ` Clément Pit--Claudel
2016-03-28 20:32 ` Óscar Fuentes
2016-03-28 20:33 ` Stephan Mueller
2016-03-28 20:17 ` Marcin Borkowski
2016-03-28 18:51 ` Lars Magne Ingebrigtsen
2016-03-28 19:22 ` Stefan Monnier
2016-03-28 19:27 ` Lars Magne Ingebrigtsen
2016-03-28 19:32 ` Dmitry Gutov
2016-03-28 20:16 ` Clément Pit--Claudel
2016-03-28 20:22 ` Lars Magne Ingebrigtsen
2016-03-28 21:43 ` Stefan Monnier
2016-03-29 8:53 ` Florian Weimer
2016-03-29 13:14 ` Phillip Lord
2016-03-29 13:39 ` Stefan Monnier
2016-03-29 15:30 ` Lars Magne Ingebrigtsen
2016-04-03 23:05 ` John Wiegley
2016-04-03 23:29 ` Clément Pit--Claudel
2016-04-03 23:30 ` John Wiegley
2016-04-03 23:44 ` Óscar Fuentes
2016-04-04 0:20 ` Clément Pit--Claudel
2016-04-04 0:29 ` Óscar Fuentes
2016-04-04 5:21 ` Lars Magne Ingebrigtsen
2016-04-04 5:26 ` John Wiegley [this message]
2016-03-29 22:26 ` Phillip Lord
2016-04-03 23:05 ` John Wiegley
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=m2fuv29c6s.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=ofv@wanadoo.es \
/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.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).