Timeline for Display all setq possibilities
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 18, 2019 at 6:15 | vote | accept | n1k31t4 | ||
| Oct 16, 2015 at 21:56 | answer | added | phils | timeline score: 4 | |
| Oct 15, 2015 at 6:59 | comment | added | xuchunyang | @DexterMorgan osx-dictionary-dictionary-choice now supports a list of dictionaries, such as (setq osx-dictionary-dictionary-choice '("Simplified Chinese" "Apple")). (I have just implemented this). | |
| Oct 14, 2015 at 23:14 | history | edited | Drew | edited tags | |
| Oct 14, 2015 at 23:13 | answer | added | Drew | timeline score: 9 | |
| Oct 14, 2015 at 21:27 | comment | added | n1k31t4 | I haven't found anything on Emacs SE from my point of view, i.e. a user looking to find the variables, as opposed to someone who is creating a package (which are of course goes into too much detail). If either of you want to write an answer, I will accept it. Otherwise I will write one sometime soon and accept that. | |
| Oct 14, 2015 at 21:22 | comment | added | Kaushal Modi | @DexterMorgan Yes, the Customize buffers will not show all the variables. They will show only the variables the package author thought will be useful for the user to customize. Such variables are declared using the defcustom form instead of defvar or defconst. | |
| Oct 14, 2015 at 21:08 | comment | added | n1k31t4 | According to Ergoemacs these 'custom' menus do not show all possible customisations! | |
| Oct 14, 2015 at 20:54 | comment | added | lawlist | Consider searching this forum for customize-group and if you find an answer on point, then you can delete the question. If you don't find an answer directly on point, consider writing up a thesis/answer on how to determine the name of a particular group available for customization based upon an installed library, so it is not necessary to surf through the various groups or open the source code to figure it out. I don't actually know the answer and found it by searching for the defcustom in the source code and then saw which :group was assigned. A :group could be the library name. | |
| Oct 14, 2015 at 20:52 | comment | added | n1k31t4 | Excellent - thank you. Would you recommend deleting the question (yes, I am embarrassed), or maybe just rewording and shortening it to make it more straight-forward for the next newbie? | |
| Oct 14, 2015 at 20:49 | comment | added | lawlist | The library you are using as an example defines the customization group as osx-dictionary. If you use the M-x customize-group interface, you can see everything the author has intended that the user be able to customize. There are three (3) items in this example. You can also simply type M-x customize and surf through the various groups. | |
| Oct 14, 2015 at 20:46 | comment | added | n1k31t4 | Is the answer maybe that some packages simply lack thorough documentation, and that reading through the code is necessary? I do understand this is open-source, so one cannot assume to have his hand held for everything - I am very grateful that people make there code free to the community! | |
| Oct 14, 2015 at 20:45 | comment | added | Kaushal Modi | The variables of packagename-- format are for the package-internal use only and not intended to be modified directly by the user. | |
| Oct 14, 2015 at 20:42 | history | asked | n1k31t4 | CC BY-SA 3.0 |