Indeed, in my workflow, the effort estimate of an item is independent of the
effort estimates of all its subitems. It thus does not makes to sum them up,
and indeed the "{:}" in the column view format causes the (independent) effort
estimate to be overwritten by the sum of the efforts of its subitems every time
column view is turned on.
From our previous attempts to get S/MIME working when using Outlook, the
function `mm-copy-to-buffer` had been adviced to change all LF to CRLF, to allow
`mm-copy-to-buffer` to find the beginning of the body. However, when the body
itself is binary and accidentally contains an CRLF, that content is modified as
well. This might break the content, as it happend with the signature of
elpa.gnu.org, which indeed contained an CRLF.
We are now a bit more non-invasive and replace the original version of
`mm-copy-to-buffer` with one that explicitly also searches for ^\r\n in addition
to just ^\n. Let's see how good that will work. Signature checking for
elpa.gnu.org is functioning again, and S/MIME still seems to be working.
This allows easier updates of this list, without having resort to executing the
corresponding code manually. In the future, we could even update that list
automatically by attaching the new function to some of projectile's hooks or
something.
The main motivation is me often mistyping S-SPC for SPC, loosing my current
candidates and frustrating myself. This is even more frustrating when inserting
text into non-selection inputs (org-capture), which is why we had disabled ivy
completion for org-capture previously. Since we are no using
ivy--regex-ignore-order for candidate regex building anyway, input restriction
is not necessary anymore, and so we remove the shortcut altogether.
This reverts commit 2622b048b6.
The main annoyance has been completion in org source blocks, and this has been
disabled now. Additionally, `company-complete` only seems to work when
company-mode is enabled. So let's enable it again and see how far we get.
When company is active, this leads to completions offered as a first step in
shell blocks, for example, which is both unnecessary and triggers a bug in
ivy (the cursor is invisible afterwards). Furthermore, this completion is
almost always unnecessary, as the snippets a usually either quite simple or
copied from elsewhere. If completion is still required, editing the code block
within the native major mode (C-c ') should be sufficient.
Most of the time, I just want to see the text and edit it, and thus I open HTML
files in Emacs anyway (usually rendering them via `shr-render-buffer`).
It's confusing me that the output of pandoc is a document fragment by default,
so let's instruct Emacs to generated complete, standalone documents instead.
Apparantly, when Gnus starts up for the first time, this function seems to be
undefined, because we are calling gnus-registry-initialize quite late in the
init process. Let's try to fix this by having this autoload.
Outlook seems to expect CRLF in S/MIME signed+encrypted mails, so we add those
somewhere in the process of encoding the mail. Furthermore, Outlook is sending
MIME messages with CRLF line endings, and we have to take care of that when
looking for the end headers.
The changes proposed here are preliminary and subject to further testing.
Let's group configuration related to MIME decoding and MIME encoding, to better
understand what these variables are actually doing and to decrease maintanence
complexity.
Scoring didn't work in my IMAP mailing list folders, but not it should. In all
other folders, as long as there is no scoring file, nothing should happen.
Flycheck used to be activated unconditionally, resulting in annoying warnings
when evaluating Lisp expressions in the minibuffer with `pp-eval-expression`,
and in the scratch buffer.
If `sandbox/.emacs.d` already exists, calling `ln` again seems to create links
within this directory. Ensure that this does not happen anymore by deleting the
link first if it already exists. Also add `-T` to `ln` to ensure its arguments
are interpreted properly.
They day I understand argument interpretation in `ln` will be a good day …
This starts emacs in the local copy of the .emacs.d directory we are currently
in, by creating a new `sandbox` directory as home directory, linking the current
directory as `.emacs.d` into there, and starting emacs.