From: Carsten Dominik <email@example.com> To: Manish <firstname.lastname@example.org> Cc: emacs org-mode mailing list <email@example.com> Subject: Re: POLL: the 40 variables project Date: Fri, 30 Jan 2009 00:07:42 +0100 [thread overview] Message-ID: <3CA13AF2-AFF7-49D1-97B6-7AF5AF6C1301@uva.nl> (raw) In-Reply-To: <firstname.lastname@example.org> On Jan 29, 2009, at 6:56 PM, Manish wrote: > On Thu, Jan 29, 2009 at 2:19 PM, Carsten Dominik wrote: >> Hi, >> >> yesterday I did this command in my org-mode git repo: >> >> grep defcustom lisp/*el |wc -l >> >> and got 378 as an answer. 378 user-customizable variables, >> no kidding. >> >> However, I bet that only about 10% of these are really used >> by more that one user :-). So when a new users starts digging >> into Org-mode, they simply must be confused by the amount >> of variables that can be set. >> >> So here is the idea: I would like to find out which variables >> users actually customize. This could be the basis >> for a great article on Worg, describing just these selected >> variables. >> >> In addition, I could make a special customization group which only >> contains those variables (Emacs allows to put a variable into several >> groups). It would be awesome to have, and a much easier start into >> customizing Org. > > This is going to be very useful, IMHO. > >> >> So here is my question to all of you. Could you, in reply to this >> message, list all the Org-related variables that you have customized, >> along with the values you used? >> >> If you want to do more, I'd also love to see comments on >> >> - why you set the variable like this >> - if you feel that the default value of that variable >> should be different >> - Any other comments you might what to give. >> >> Of course, if there is a volunteer who would like to organize >> this info into a Worg page, I would even be more happy ... > > I am collating the information in the following format. > > | Submitter | Variable | Value | Comment | Hi Manish, thanks so much for doing this, really appreciate it. Maybe add a column with the default value, so that we can be sure that the did not just set the default value? But this is not important, we can do this automatically when we mine that data. - Carsten > > > Further analyses like which were the most commonly customized > variables, > their values etc. can then be derived from the listing (may be using R > or Excel.) Ideas on how to better organize this data are welcome. > > So far we have 13 responses. > > -- > Manish
next prev parent reply other threads:[~2009-01-29 23:07 UTC|newest] Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-01-29 8:49 Carsten Dominik 2009-01-29 11:13 ` Friedrich Delgado Friedrichs 2009-01-29 13:02 ` Carsten Dominik 2009-01-29 13:40 ` Dan Griswold 2009-01-29 11:46 ` Womick, Don 2009-01-29 11:59 ` Tassilo Horn 2009-01-29 13:37 ` Sebastian Rose 2009-01-29 13:30 ` Bernt Hansen 2009-01-29 13:46 ` Chris Leyon 2009-01-29 14:10 ` Matthew Lundin 2009-01-29 14:49 ` Bernt Hansen 2009-01-29 14:55 ` srandby 2009-01-29 16:01 ` Eric S Fraga 2009-01-29 16:40 ` Dan Davison 2009-01-29 16:40 ` Michael Ekstrand 2009-01-29 17:24 ` Sivaram Neelakantan 2009-01-29 17:56 ` Manish 2009-01-29 21:02 ` Dan Davison 2009-01-29 23:07 ` Carsten Dominik [this message] 2009-01-30 7:46 ` Manish 2009-01-30 8:18 ` Carsten Dominik 2009-01-30 8:29 ` Manish 2009-01-30 8:38 ` Carsten Dominik 2009-01-30 8:52 ` Manish 2009-01-30 9:16 ` Carsten Dominik 2009-01-30 10:35 ` Scot Becker [not found] ` <email@example.com> 2009-02-01 22:15 ` Carsten Dominik 2009-02-02 10:36 ` Carsten Dominik [not found] ` <firstname.lastname@example.org> 2009-01-30 13:50 ` Carsten Dominik 2009-01-30 15:27 ` Carsten Dominik 2009-01-29 18:02 ` William Henney 2009-01-29 19:07 ` Peter Jones 2009-01-29 19:44 ` Hsiu-Khuern Tang 2009-01-29 22:06 ` Steven E. Harris 2009-01-29 22:43 ` Oliver Charles 2009-01-30 3:32 ` Ross Patterson 2009-01-30 12:13 ` Sebastian Rose 2009-01-30 3:44 ` Dennis Groves 2009-01-30 4:12 ` Manish 2009-01-30 4:46 ` Austin Frank 2009-01-30 8:17 ` Ulf Stegemann 2009-01-30 12:26 ` Sebastian Rose 2009-01-30 8:26 ` Cameron Horsburgh 2009-01-30 8:43 ` R: " Giovanni Ridolfi 2009-01-30 9:21 ` Manish 2009-01-30 11:09 ` Shaun Johnson 2009-01-30 12:08 ` Rainer Stengele 2009-01-30 12:48 ` Mikael Fornius 2009-01-30 15:56 ` William Henney 2009-01-30 16:12 ` Christian Egli 2009-01-30 16:34 ` Manuel Hermenegildo 2009-02-01 0:34 ` Samuel Wales 2009-01-30 16:36 ` Eric Schulte 2009-01-31 13:06 ` Martin Stemplinger 2009-02-01 15:18 ` James TD Smith 2009-02-04 15:29 ` Charles Sebold 2009-02-05 14:55 ` Manish 2009-02-04 21:28 ` Mike Newman 2014-01-17 20:55 ` [Orgmode] " Manish 2014-01-19 15:54 ` Bastien 2014-01-20 2:18 ` M 2014-01-20 11:17 ` Bastien 2014-01-20 11:38 ` Rainer M Krug 2014-01-20 11:47 ` Bastien 2014-01-20 17:07 ` Eric S Fraga 2014-01-20 7:05 ` henry atting 2014-01-20 11:16 ` Bastien 2014-04-30 15:29 ` Sungmin 2014-04-30 15:50 ` Eric S Fraga [not found] <20090130091800.B54F32868C@mailhost.cs.tu-berlin.de> 2009-01-30 11:33 ` Stephan Schmitt
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.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=3CA13AF2-AFF7-49D1-97B6-7AF5AF6C1301@uva.nl \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: POLL: the 40 variables project' \ /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
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.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 NNTP newsgroup(s).