2

Try setting C-hv erc-track-exclude-types For me, the original value was ("NICK" "333" "353") and I have it set to: ("JOIN" "KICK" "NICK" "PART" "QUIT" "MODE" "333" "353") The numeric values can be specific to the IRC daemon you are connected to, and might entail trial and error on your part to figure out which values are creating noise for you. e.g. The ...


2

You can modify the command line arguments in an init file if you want. But if you do that after Emacs has processed the argument, it won't have any effect. Emacs processes command line arguments in two places: in the C startup code, and in startup.el. The C startup code processes arguments before it executes any Lisp code, so there's no way to influence ...


2

Is it possible to set Emacs start-up command-line flags such as -nw and -q in an init file? If it is, how can I do that? In general, no, you can't do that -- and your second example option is precisely what I would have used to explain why: -q (aka --no-init-file) tells Emacs not to load your init file, so trying to set that option in your init file does ...


1

If this is on account of erc-notifications-mode generating a notification because your nick was mentioned in the channel (on account of being listed in "*** Users on ..." message), then you'll have to dig into that functionality. Or just disable the mode with (erc-notifications-mode 0) or similar to disable all notifications. If that's the reason, then erc-...


1

The lexical-binding settings of the files loaded with load and require are not affected by the (buffer-local) lexical-binding setting of the init file. Warning: But, a change of lexical-binding in the init file can cause errors there. Example for a change through lexical-binding t: (setq var-a 0) (defun a () (message "a: %s" var-a)) (defun b () (let ...


1

For answering why after-change-functions becomes nil I cite a paragraph of the doc-string of after-change-functions: If an unhandled error happens in running these functions, the variable's value remains nil. That prevents the error from happening repeatedly and making Emacs nonfunctional. Turn on the switch "Enter Debugger on Error" in the "Options"...


1

I've had the same issue with my org settings file. The reason behind was that I used #+BEGIN_SRC elisp instead of #+BEGIN_SRC emacs-lisp. Therefore, the function org-babel-load-file considered that there was no elisp code to execute and return nil. I wasn't aware of that solution early because the code highlight was activated. According to this answer, ...


Only top voted, non community-wiki answers of a minimum length are eligible