> I don't know about you, but that's just a complete mess for me and a big
> nope. Also: it still hides information.
>
> If you have better suggestions let me know :)

I take your point regarding all of these options. Perhaps the best
approach is some sort of pop-up, although the ability to copy (as in,
copy and paste) the addresses would be very useful. Maybe simply cat-ing 
a list to a new terminal window?

---
Matthew Lemon

> This thread resulted in the addition of a new command: ':envelope'. You can do
> this in the message viewer and get a popup of the Envelope data.

Sadly, I do not seem to have an :envelope command available (v0.13.0).

---
Matthew Lemon

Hi - given the inability to wrap the To field, is there any alternative
approach to obtaining a cleanly-presented list of emails in this field?
Still configuring and learning aerc - am new to the game. Thanks!

---
Matthew Lemon

>> Yes, please go ahead.  Note that tomorrow I will prepare version 1.2.0

>> (unless I discover some last minute bug).
>
> I will submit a change over the weekend. No worries if it misses any
> deadline.

Please find attached a suggested patch.

Rather than disrupt your existing config examples, (which uses
default-directory) I have added a paragraph pointing out the possibility
to use an absolute path, and an associated example. I looked through the
documentation for similar "qualification" or "NB" style paragraphs and

Hi,

I would like to suggest a slight clarification to the documentation for
denote, related to the configuration of separated directies as
'silos'. This is great feature, but I was slightly tripped-up by having
a subdirectory inside the `denote-directory`, referenced in the
`.dir-locals.el` file; links inside notes within the subdirectory are
unable to find the path to notes in the parent directory (or, you are
not able to create links to the parent at all) because I blindly copied
and pasted the suggested elisp in the docs into my config:

```
;;; Directory Local Variables.  For more information evaluate:
;;;

---
 matt | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 matt

diff --git a/matt b/matt
new file mode 100644
index 0000000..b4380e4
--- /dev/null
+++ b/matt
@@ -0,0 +1 @@
+I'm about to try git send-email!
-- 
2.39.0
[message trimmed]

---
 matt | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 matt

diff --git a/matt b/matt
new file mode 100644
index 0000000..e6bc5e9
--- /dev/null
+++ b/matt
@@ -0,0 +1 @@
+I am about to try git send-email!
-- 
2.39.0
[message trimmed]

---
 matt | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 matt

diff --git a/matt b/matt
new file mode 100644
index 0000000..600551a
--- /dev/null
+++ b/matt
@@ -0,0 +1 @@
+I have succcessfully used git send-email!
-- 
2.39.0
[message trimmed]

---
 matt | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 matt

diff --git a/matt b/matt
new file mode 100644
index 0000000..6d0ecfd
--- /dev/null
+++ b/matt
@@ -0,0 +1 @@
+I'm about to try git send-email
-- 
2.39.0
[message trimmed]

-- 
Protesilaos Stavrou <info@protesilaos.com> writes:

> On Friday I plan to prepare Denote's version 1.2.0.  If you want to
> contribute your custom code to the manual, we can do it right after.
> This will give us plenty of time to test the code and, perhaps, think of
> ways to expand on it.

Happy to look at that - look forward to version 1.2.0.

> It loooks good to me.  A simple optimisation is to avoid calling the
> same function multiple times to fetch data.  Here is the gist:
>