Docs: Update readme #273
Merged
Docs: Update readme #273
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Darn, Github doesn't like what I did with the https://github.com/phil-s/ement.el/tree/phil-s/docs?tab=readme-ov-file#room-buffers I'll see if I can figure out a fix for that... |
Along similar lines to (info "(org)Escape Character") I've introduced a ZERO WIDTH JOINER character after the apostrophe in ~C-c '~ in order to achieve the correct appearance in both Emacs and Github. This can be visualised using (set-face-background 'glyphless-char "red"). I've substituted S-<return> everywhere that S-RET appeared, as the latter isn't a valid representation.
|
That was a pain -- I think I now understand why the text had previously been written as Through trial-and-error I've found that a single ZERO WIDTH JOINER after the apostrophe in |
The reply functionality has changed since that was written, and an active region no longer has any bearing on the quoted text.
I prefer the Oxford comma. :)
|
Thank you. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Per
(info "(org)Escape Character")I've introduced a zero-width space before the closing paren in "(while writing in minibuffer: ~C-c '~)" in order to achieve the correct formatting. This can be visualised using(set-face-background 'glyphless-char "red").I've substituted
S-<return>everywhere thatS-RETappeared, as the latter isn't a valid representation.