Fixing syntax errors in mu4e.texi
This commit is contained in:
@ -3208,7 +3208,7 @@ with other tools.
|
|||||||
* Speedbar::A special frame with your folders
|
* Speedbar::A special frame with your folders
|
||||||
* Dired:: Attaching files using @t{dired}
|
* Dired:: Attaching files using @t{dired}
|
||||||
* Hydra:: Custom shortcut menus
|
* Hydra:: Custom shortcut menus
|
||||||
* iCal integration:: Enabling iCalendar invite processing in mu4e
|
* iCalendar Integration:: Enabling iCalendar invite processing in mu4e
|
||||||
@end menu
|
@end menu
|
||||||
|
|
||||||
@node Emacs default
|
@node Emacs default
|
||||||
@ -3495,8 +3495,8 @@ With Hydra installed, we can add multi-character shortcuts, for instance:
|
|||||||
Now, you can bind a convenient key to my-mu4e-bookmarks/body.
|
Now, you can bind a convenient key to my-mu4e-bookmarks/body.
|
||||||
@end lisp
|
@end lisp
|
||||||
|
|
||||||
@node iCalendar Integration, , Hydra, Other Tools
|
@node iCalendar Integration
|
||||||
@section iCalendar
|
@section iCalendar Integration
|
||||||
|
|
||||||
By default, mu4e presents iCalendar invitations as .vcs file
|
By default, mu4e presents iCalendar invitations as .vcs file
|
||||||
attachments. Experimental support is available to parse these
|
attachments. Experimental support is available to parse these
|
||||||
@ -3514,13 +3514,13 @@ The minimal setup is:
|
|||||||
@lisp
|
@lisp
|
||||||
(require 'mu4e-icalendar)
|
(require 'mu4e-icalendar)
|
||||||
(mu4e-icalendar-setup)
|
(mu4e-icalendar-setup)
|
||||||
@end
|
@end lisp
|
||||||
|
|
||||||
To add the event to a diary file of your choice:
|
To add the event to a diary file of your choice:
|
||||||
|
|
||||||
@lisp
|
@lisp
|
||||||
(setq mu4e-icalendar-diary-file "/path/to/your/diary")
|
(setq mu4e-icalendar-diary-file "/path/to/your/diary")
|
||||||
@end
|
@end lisp
|
||||||
|
|
||||||
To enable optional functionality to capture iCalendar events to your org files:
|
To enable optional functionality to capture iCalendar events to your org files:
|
||||||
|
|
||||||
@ -3529,7 +3529,7 @@ To enable optional functionality to capture iCalendar events to your org files:
|
|||||||
(setq gnus-icalendar-org-capture-file "~/org/notes.org")
|
(setq gnus-icalendar-org-capture-file "~/org/notes.org")
|
||||||
(setq gnus-icalendar-org-capture-headline '("Calendar"))
|
(setq gnus-icalendar-org-capture-headline '("Calendar"))
|
||||||
(gnus-icalendar-org-setup)
|
(gnus-icalendar-org-setup)
|
||||||
@end
|
@end lisp
|
||||||
|
|
||||||
NOTE: both the capture file and the headline(s) inside must already
|
NOTE: both the capture file and the headline(s) inside must already
|
||||||
exist.
|
exist.
|
||||||
@ -3548,7 +3548,7 @@ between the two modes. You can do this with the following:
|
|||||||
(mu4e-headers-view-message))
|
(mu4e-headers-view-message))
|
||||||
|
|
||||||
(define-key mu4e-view-mode-map "i" 'mu4e-toggle-gnus-view)
|
(define-key mu4e-view-mode-map "i" 'mu4e-toggle-gnus-view)
|
||||||
@end
|
@end lisp
|
||||||
|
|
||||||
@node Example configs
|
@node Example configs
|
||||||
@appendix Example configs
|
@appendix Example configs
|
||||||
|
|||||||
Reference in New Issue
Block a user