1. RC File Location
variable_name = value;
But as your rc grows in size, with more and more and customizations, you may find the reinit command to be a blunter instrument than you wish. To use it successfully, you often have to write side-effectual code in non-idiomatic or obfuscated ways to protect against the effects of repeat evaluation. For those who have reached this level, we recommend evaluating only parts of your code at a time. You can use M-: for the trivial cases, and we highly recommend MozRepl for more in-depth hacking sessions. Happy hacking!
Comment out the contents of your rc (with /* and */) and put a dumpln call at the beginning, like dumpln("hello, world!");. See if the text is printed to the terminal.
Start Conkeror and browse to about:config. See if you have inadvertently set a value for the pref conkeror.rcfile. If you have, clear it and try again.
5. Changing the RC Location
Most people don't need to change the location of their rc. If you are thinking of doing so simply because you haven't gotten your rc working yet, STOP, because you will only complicate the situation for yourself. If, on the other hand, you have other reasons for changing the rc location, and you completely understand how it works and why you want to do so, go ahead.
You change your rc by doing:
M-: user_pref('conkeror.rcfile', '/home/foo/conkeror-rc'); RET
or from the command line:
conkeror -q -batch -e "user_pref('conkeror.rcfile', '/home/foo/conkeror-rc');"
If conkeror.rcfile is set to the empty string, Conkeror will not attempt to load any rc.
5.1. Attn: Windows users
6. Editing the RC
- Syntax coloring;
- A command that sends statements to be evaluated by conkeror (bound to "C-c C-c");
- Indentation of macros.