From: hector <hectorlahoz@gmail.com>
To: Skip Montanaro <skip.montanaro@gmail.com>, narendraj9@gmail.com
Cc: help-gnu-emacs@gnu.org
Subject: Re: Requiring elisp that comes with Emacs
Date: Wed, 1 Feb 2017 11:07:07 +0100 [thread overview]
Message-ID: <20170201100707.GB2388@workstation> (raw)
In-Reply-To: <CANc-5Uz28xHqhM6-Kg66B_4GOzAFChvtAX7bRs=yf5ZzjuNmkA@mail.gmail.com>
That's a very good answer. This is how life (and society) works.
I am a do-it-yourself kind of guy. I guess that's why I like Emacs
and free software in general.
But sometimes you must accept you can't do EVERYTHING by yourself.
On Tue, Jan 31, 2017 at 02:40:55PM -0600, Skip Montanaro wrote:
> > Why would you let someone else manage it for you?
>
> This is not really an Emacs question. It is more of a quality of life
> question. Still, since you asked...
>
> I let someone else manage my Emacs installations for the same reasons that:
>
> - I no longer rebuild my Linux kernel daily (as I used to 20 or more
> years ago)
> - I rely on a third party to maintain a complex Python environment
> (despite having been one of the core Python developers in dim, dark the
> past)
> - Let the mechanic do tune-ups on my car
>
> There is value in stability and knowing when others are better at a
> particular task than I am (or at least good enough that I can delegate to
> them). I can't be an expert in everything. Sometimes, even if I know I can
> do the job myself, it's worth it to let someone else do it, because time -
> as they say - is money. If I'm fiddling with my Emacs installation or
> changing the oil in my car, that's time when I could have been doing
> something else of more personal value to me, like working on paying work,
> riding my bike, or having dinner with my wife. I have more important things
> to do with my time than fiddle with a complex tool chain on a continuous
> (or even occasional) basis.
>
> S
>
> On Tue, Jan 31, 2017 at 2:01 PM, Narendra Joshi <narendraj9@gmail.com>
> wrote:
>
> > Skip Montanaro <skip.montanaro@gmail.com> writes:
> >
> > > (require) a fewpackages in my .emacs file: mouse,
> > > auto-complete-config, and lua-mode. I didn't install any of them
> > > (someone else manages my local Emacs installation), so they may not
> >
> > That's interesting. Why would you let someone else manage it for you?
> >
> > - Narendra
> >
next prev parent reply other threads:[~2017-02-01 10:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 16:52 Requiring elisp that comes with Emacs Narendra Joshi
2017-01-30 18:50 ` Skip Montanaro
2017-01-31 13:46 ` Narendra Joshi
2017-01-31 14:39 ` Óscar Fuentes
2017-01-31 18:06 ` Skip Montanaro
2017-01-31 20:03 ` Óscar Fuentes
2017-01-31 14:50 ` Skip Montanaro
2017-01-31 20:01 ` Narendra Joshi
2017-01-31 20:40 ` Skip Montanaro
2017-02-01 10:07 ` hector [this message]
2017-02-01 15:10 ` Narendra Joshi
2017-02-01 15:53 ` Eric Abrahamsen
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=20170201100707.GB2388@workstation \
--to=hectorlahoz@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=narendraj9@gmail.com \
--cc=skip.montanaro@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).