summaryrefslogtreecommitdiffhomepage
path: root/blog/entry/gnus+notmuch.mdwn
diff options
context:
space:
mode:
authorSean Whitton <spwhitton@spwhitton.name>2022-07-11 10:09:44 -0700
committerSean Whitton <spwhitton@spwhitton.name>2022-07-11 18:23:43 -0700
commit97b64b0012ad553fa4db5fd1007582dd7e89eb02 (patch)
treeebbdcbfea0c8945ea1744f30c52476795f0143df /blog/entry/gnus+notmuch.mdwn
parent9bacc0a0b924bd9a3aea006dbbf8a66232121cfa (diff)
downloadwiki-97b64b0012ad553fa4db5fd1007582dd7e89eb02.tar.gz
attempt to fix indentation
Diffstat (limited to 'blog/entry/gnus+notmuch.mdwn')
-rw-r--r--blog/entry/gnus+notmuch.mdwn54
1 files changed, 28 insertions, 26 deletions
diff --git a/blog/entry/gnus+notmuch.mdwn b/blog/entry/gnus+notmuch.mdwn
index dc8793a..d3d99aa 100644
--- a/blog/entry/gnus+notmuch.mdwn
+++ b/blog/entry/gnus+notmuch.mdwn
@@ -24,22 +24,23 @@ always more comfortable with less Unix and more Lisp when it's feasible.
I have some code running in `gnus-started-hook` which does something like
this for each saved search:
- ``` {.elisp}
- (if (gnus-group-entry group)
- (gnus-group-set-parameter group 'nnselect-specs ...)
- (gnus-group-make-group ...))
- ```
+ ``` {.elisp}
+ (if (gnus-group-entry group)
+ (gnus-group-set-parameter group 'nnselect-specs ...)
+ (gnus-group-make-group ...))
+ ```
- The idea is that if you update your saved search in your init.el, rerunning
- this code will update the entries in the group buffer. An alternative would
- be to just kill every nnselect search in the group buffer each time, and
- then recreate them. In addition to reading `gnus-group-make-search-group`,
- you can look in `~/.newsrc.eld` to see the sort of `nnselect-specs` group
- parameters you'll need your code to produce.
+ The idea is that if you update your saved search in your init.el,
+ rerunning this code will update the entries in the group buffer. An
+ alternative would be to just kill every nnselect search in the group
+ buffer each time, and then recreate them. In addition to reading
+ `gnus-group-make-search-group`, you can look in `~/.newsrc.eld` to see the
+ sort of `nnselect-specs` group parameters you'll need your code to
+ produce.
- I've very complicated generation of my saved searches from some variables,
- but that's something I had when I was using notmuch.el, too, so perhaps I'll
- describe some of the ideas in there in another post.
+ I've very complicated generation of my saved searches from some variables,
+ but that's something I had when I was using notmuch.el, too, so perhaps
+ I'll describe some of the ideas in there in another post.
- You'll likely want to globally bind a function which starts up Gnus if it's
not already running and then executes an arbitrary notmuch search. For that
@@ -53,19 +54,20 @@ always more comfortable with less Unix and more Lisp when it's feasible.
want to programmatically generate a topics topology. This is how you do
that:
- ``` {.elisp}
- (with-current-buffer gnus-group-buffer
- (gnus-topic-mode 0)
- (setq gnus-topic-alist nil gnus-topic topology nil)
- ;; Now push to those two variables. You can also use
- ;; `gnus-topic-move-matching' to move nnmaildir groups into, e.g., "misc".
- (gnus-topic-mode 1)
- (gnus-group-list-groups))
- ```
+ ``` {.elisp}
+ (with-current-buffer gnus-group-buffer
+ (gnus-topic-mode 0)
+ (setq gnus-topic-alist nil gnus-topic topology nil)
+ ;; Now push to those two variables. You can also use
+ ;; `gnus-topic-move-matching' to move nnmaildir groups into, e.g.,
+ ;; "misc".
+ (gnus-topic-mode 1)
+ (gnus-group-list-groups))
+ ```
- If you do this in `gnus-started-hook`, the values for those variables Gnus
- saves into `~/.newsrc.eld` are completely irrelevant and do not need backing
- up/syncing.
+ If you do this in `gnus-started-hook`, the values for those variables Gnus
+ saves into `~/.newsrc.eld` are completely irrelevant and do not need
+ backing up/syncing.
- When you want to use `M-g` to scan for new mail in a saved search, you'll
need to have Gnus also rescan your nnmaildir inbox, else it won't know about