unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "John Wiegley" <johnw@gnu.org>
To: Philippe Vaucher <philippe.vaucher@gmail.com>
Cc: "Elias Mårtenson" <lokedhs@gmail.com>,
	"Stefan Monnier" <monnier@iro.umontreal.ca>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: custom-set-variables considered harmful
Date: Tue, 28 Nov 2017 08:50:34 -0800	[thread overview]
Message-ID: <m28teql545.fsf@D-69-91-135-157.dhcp4.washington.edu> (raw)
In-Reply-To: <CAGK7Mr50CTUxGgUV-O1kqYY6u0oCPTRf-dXkXxp8qZcW3Ep_tw@mail.gmail.com> (Philippe Vaucher's message of "Tue, 28 Nov 2017 15:12:46 +0100")

>>>>> "PV" == Philippe Vaucher <philippe.vaucher@gmail.com> writes:

VP> The problem I have with c-s-v is that I don't see its benefits for configs
VP> like this:

Just FYI, in the latest use-package (on github) you can now say:

  (use-package ido
    :bind ("C-b" . ido-switch-buffer)
    :custom ((ido-enable-flex-matching t)
             (ido-create-new-buffer 'always)
             (ido-use-url-at-point nil)
             (ido-use-filename-at-point nil)
  
             ;; Disable auto searching for files unless called explicitly   
             (ido-auto-merge-delay-time 99999)
  
             ;; Avoid "size too big" errors
             (ido-max-directory-size 300000)
  
             ;; Always propose old buffers as well
             (ido-use-virtual-buffers nil)
  
             ;; Don't remember history
             (ido-enable-last-directory-history nil))
    :config
    (ido-mode t)
    (ido-everywhere t))

Which uses custom-set-variables under the hood, taking advantage of any :set
functions related to those variables.

-- 
John Wiegley                  GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com                          60E1 46C4 BD1A 7AC1 4BA2



  reply	other threads:[~2017-11-28 16:50 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-04 17:10 custom-set-variables considered harmful Stefan Monnier
2017-11-06  9:02 ` Philippe Vaucher
2017-11-06 12:19   ` Clément Pit-Claudel
2017-11-06 16:36   ` raman
2017-11-07 19:53     ` Stefan Monnier
2017-11-08 10:06 ` Vivek Dasmohapatra
2017-11-08 13:38   ` Stefan Monnier
2017-11-08 14:23     ` Vivek Dasmohapatra
2017-11-08 15:17       ` Stefan Monnier
2017-11-08 15:34         ` Vivek Dasmohapatra
2017-11-13 16:26 ` Stefan Monnier
2017-11-24  7:04   ` Elias Mårtenson
2017-11-24  7:16     ` Stefan Monnier
2017-11-24 17:37       ` Clément Pit-Claudel
2017-11-24 17:56         ` Stefan Monnier
2017-11-26 12:15       ` Elias Mårtenson
2017-11-26 16:30         ` Drew Adams
2017-11-28 14:12         ` Philippe Vaucher
2017-11-28 16:50           ` John Wiegley [this message]
2017-12-01  9:44             ` Philippe Vaucher
2017-11-29  3:36           ` Elias Mårtenson
2017-11-29 15:00             ` Stefan Monnier
2017-11-29 15:03               ` Drew Adams
2017-12-01 20:42                 ` Robert Weiner
2017-12-02  0:10                   ` Richard Stallman
2017-12-02  1:58                     ` Drew Adams
2017-12-02  5:56                 ` Teemu Likonen
2017-11-29 16:35               ` Elias Mårtenson
2017-11-29 19:57                 ` Scott Randby
2017-11-29 22:08                   ` Stefan Monnier
2017-11-30  0:40                     ` Scott Randby
2017-12-01  9:51             ` Philippe Vaucher
2017-12-04 13:48   ` Stefan Monnier
2017-12-04 15:36     ` Eli Zaretskii
2017-12-04 16:05     ` Robert Weiner
2017-12-04 23:50     ` Richard Stallman
2017-12-05  1:45       ` Stefan Monnier
2017-11-23 20:12 ` 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=m28teql545.fsf@D-69-91-135-157.dhcp4.washington.edu \
    --to=johnw@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lokedhs@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=philippe.vaucher@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.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).