Skip to content

Conversation

@ernstki
Copy link

@ernstki ernstki commented Dec 6, 2025

There wasn't a lot to go on here, nor in the man page, so I took it upon myself to add a few more examples to the IMAP part of usingcurl/reademail.md. Mostly so I could have something to refer back to later, since this IMAP stuff didn't stick very well in my brain the first couple times.

This IMAP cheatsheet helped me out a lot, and I'd be happy to add another commit to add that as a reference, if desired.

@ernstki ernstki force-pushed the expand-reademail-imap branch from 8f4e18c to 481c6d9 Compare December 6, 2025 23:09
@ernstki ernstki marked this pull request as draft December 6, 2025 23:17
This produces output similar to what's below; the numbers after the asterisks
are the **mailbox indices** of the messages, counting from 1:

* 1 FETCH (FLAGS (\Flagged \Deleted \Seen) INTERNALDATE " 3-Dec-2025 12:02:39 -0500" RFC822.SIZE 15163)
Copy link
Author

@ernstki ernstki Dec 6, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These lines represent output from a command. Not sure I would want it wrapped just to appease check-quotes.pl, but if this is a hard choice (e.g. because it makes the PDF look bad, or we don't want to alter the CI routines around this), I'll just ellipsize it until it fits.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All docs look weird and hard-to-read with long lines so I propose we still wrap these lines somehow.

@ernstki ernstki force-pushed the expand-reademail-imap branch from 481c6d9 to 6b998fb Compare December 6, 2025 23:35
@ernstki
Copy link
Author

ernstki commented Dec 6, 2025

@ernstki ernstki marked this pull request as ready for review December 7, 2025 17:38
Copy link
Member

@bagder bagder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for working on this! Some comments:


curl 'imap://server.example.com/fun;MAILINDEX=57'

Be aware that deleted but not "expunged" messages still have an index!
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Our checkers don't like exclamation marks much.

Suggested change
Be aware that deleted but not "expunged" messages still have an index!
Be aware that deleted but not "expunged" messages still have an index.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd actually like your permission to simply disable that linting rule (as with the typography checks), because it is not solving a real problem, and as noted here it triggers spuriously.

There is only a single exclamation point in this entire source file, and certainly that is "under control."

This produces output similar to what's below; the numbers after the asterisks
are the **mailbox indices** of the messages, counting from 1:

* 1 FETCH (FLAGS (\Flagged \Deleted \Seen) INTERNALDATE " 3-Dec-2025 12:02:39 -0500" RFC822.SIZE 15163)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All docs look weird and hard-to-read with long lines so I propose we still wrap these lines somehow.


curl 'imap://server.example.com/stuff;UID=57'

Get the 57<sup>th</sup> message from the mailbox `fun`:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since our typo script is a little silly and I would rather not add th a valid word, how about rephrasing it?

Suggested change
Get the 57<sup>th</sup> message from the mailbox `fun`:
Get message number 57 from the mailbox `fun`:

@ernstki ernstki marked this pull request as draft January 28, 2026 19:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants