[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: custom-set-variables considered harmful

From: Philippe Vaucher
Subject: Re: custom-set-variables considered harmful
Date: Tue, 28 Nov 2017 15:12:46 +0100

Note that as long as the `setq` is within the magical
custom-autogenerated-user-settings form, it will behave correctly even
if the variable has a setter function.  The difference will only affect
those users who take this code and then copy it elsewhere.

But setq doesn't have any concrete benefit other than familiarity to people who don't understand custom. I've spent more time than I wish on Freenode #emacs teaching people about custom. If c-s-v was used consistently that effort would be made a lot easier. 

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

(use-package ido
  :bind ("C-b" . ido-switch-buffer)
  (setq ido-enable-flex-matching t)
  (setq ido-create-new-buffer 'always)
  (setq ido-use-url-at-point nil)
  (setq ido-use-filename-at-point nil)

  ;; Disable auto searching for files unless called explicitly
  (setq ido-auto-merge-delay-time 99999)

  ;; Avoid "size too big" errors
  (setq ido-max-directory-size 300000)

  ;; Always propose old buffers as well
  (setq ido-use-virtual-buffers nil)

  ;; Don't remember history
  (setq ido-enable-last-directory-history nil)
  (ido-mode t)
  (ido-everywhere t))

Can you maybe enlighten me about what problem c-s-v solves that would have me start to use it?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]