alx/mu4e
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

scm.texi: some improvements in text

Browse Source
This commit is contained in:
Dirk-Jan C. Binnema
2025-10-11 21:49:25 +03:00
committed by Seth Ladygo
parent 056540b8e8
commit 20d18cb7ee
1 changed files with 20 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

29
scm/mu-scm.texi
View File

@ -483,10 +483,10 @@ Not to be confused with @code{labels} procedure for a @code{message} object.
@node Message @node Message
@section Message @section Message
A message represents the information about an e-mail message. @t{mu} gets this A @code{message} object represents the information about an e-mail message.
information either from its database (the @t{mu} store), e.g., with @code{mfind} @t{mu} gets this information either from its database (the @t{mu} store), e.g.,
(see @xref{Store}) or by reading an email message from the file-systems with with @code{mfind} (see @xref{Store}) or by reading an email message from the
@code{make-message}. file-systems with @code{make-message}.
In many of the examples below we assume there is some @code{message} object, In many of the examples below we assume there is some @code{message} object,
e.g. as retrieved through: e.g. as retrieved through:
@ -496,11 +496,22 @@ e.g. as retrieved through:
@anchor{full-message} Many of the procedures below use the internal @anchor{full-message} Many of the procedures below use the internal
representation of the message from the database; this re-uses the same representation of the message from the database; this re-uses the same
information that @code{mu4e} uses. However, that is not sufficient for all: information that @code{mu4e} uses:
@code{body} and @code{header} need the full message. To get this, it needs to
open the message file from the file-system. Much of this is internal to @itemize
@t{mu-scm}, except that full-method-procedures are a bit slower relatively to @item Basics: @code{subject}, @code{message-id}, @code{priority}
the database-only ones. @item Contact fields: @code{from}, @code{to}, @code{cc}, @code{bcc}
@item Dates: @code{date} and @code{last-change}
@item ``Meta-data'' about a message: @code{maildir}, @code{path}, @code{size}, @code{labels}
@item Miscellaneous: @code{flags}, @code{references}, @code{thread-id}, @code{mailing-list}, @code{language}
@end itemize
However, that is not sufficient for all cases: @code{body} and @code{header}
need the full message. The same is true for @code{mime-parts}.
For these methods, @code{mu} needs to open the message file from the
file-system. This is handled transparently inside @t{mu-scm}, except that
full-method-procedures are a bit slower relatively to the database-only ones.
@subsection Basics @subsection Basics