From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Michael Albinus <michael.albinus@gmx.de>
Cc: kfogel@red-bean.com, mehw.is.me@inventati.org, emacs-devel@gnu.org
Subject: RE: Add new functions to mark/unmark/delete all bookmarks
Date: Sat, 25 Jul 2020 09:07:23 -0700 (PDT) [thread overview]
Message-ID: <cd015f87-8253-490a-8e99-18842c00bc5e@default> (raw)
In-Reply-To: <<83d04jd2pm.fsf@gnu.org>>
> > In Lisp comments, objects quoted 'like-this' are not
> > highlighted. Objects quoted `like-this' are. That's why the latter
> > quotation seems to be preferred for Lisp comments, IME.
>
> What is the utility of highlighting quoted symbols in comments?
Uh, they stand out. Lisp comments can talk about
specific functions, vars, etc. Greatly improves
readability, IMO.
E.g., Contrast these comments in dired.el, which quote:
;; Note this can't simply be run inside function `dired-ls' as the hook
;; functions probably depend on the dired-subdir-alist to be OK.
;; We make heavy use of MATCH-ANCHORED, since the regexps don't identify the
;; file name itself. We search for Dired defined regexps, and then use the
;; Dired defined function `dired-move-to-filename' before searching for the
;; simple regexp ".+". It is that regexp which matches the file name.
;; Files suffixed with `completion-ignored-extensions'.
;; If a dialog is used, call `read-directory-name' so the
;; dialog code knows we want directories. Some dialogs
;; can only select directories or files when popped up,
;; not both. If no dialog is used, call `read-file-name'
;; because the user may want completion of file names for
;; use in a wildcard pattern.
;; Do not auto-revert when the dired buffer can be currently
;; written by the user as in `wdired-mode'.
;; Use point difference instead of `current-column', because
;; the former works when `dired-hide-details-mode' is enabled.
;; Always revert when `dir-or-list' is a cons. Also revert
;; if `dired-directory' is a cons but `dir-or-list' is not.
with these comments, in the same file, which don't quote:
;; Inherit from font-lock-comment-delimiter-face since with min-colors 8
;; font-lock-comment-face is not colored any more.
;; If the argument was syntactically a directory name not a file name,
;; or if it happens to name a file that is a directory,
;; convert it syntactically to a directory name.
;; The reason for checking initially-was-dirname
;; and not just file-directory-p
;; is that file-directory-p is slow over ftp.
and with this comment, which both does and doesn't quote:
;; If DIR-OR-LIST is a string and there is an existing dired buffer
;; for it, just leave buffer as it is (don't even call dired-revert).
;; This saves time especially for deep trees or with ange-ftp.
;; The user can type `g' easily, and it is more consistent with find-file.
;; But if SWITCHES are given they are probably different from the
;; buffer's old value, so call dired-sort-other, which does
;; revert the buffer.
;; Revert the buffer if DIR-OR-LIST is a cons or `dired-directory'
;; is a cons and DIR-OR-LIST is a string.
;; A pity we can't possibly do "Directory has changed - refresh? "
;; like find-file does.
;; Optional argument MODE is passed to dired-find-buffer-nocreate,
;; see there.
next parent reply other threads:[~2020-07-25 16:07 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<20200724005105.11f85d5f@pineapple>
[not found] ` <<87pn8ku3y9.fsf@red-bean.com>
[not found] ` <<20200725124618.49a073b1@pineapple>
[not found] ` <<83lfj7dfp2.fsf@gnu.org>
[not found] ` <<87tuxvpq1r.fsf@gmx.de>
[not found] ` <<83d04jd2pm.fsf@gnu.org>
2020-07-25 16:07 ` Drew Adams [this message]
2020-07-23 23:00 Add new functions to mark/unmark/delete all bookmarks Matthew White
2020-07-24 3:15 ` Drew Adams
2020-07-24 9:07 ` Matthew White
2020-07-24 15:07 ` Stefan Monnier
2020-07-24 15:18 ` Lars Ingebrigtsen
2020-07-24 17:03 ` Matthew White
2020-07-24 17:09 ` Stefan Monnier
2020-07-28 15:54 ` Matthew White
2020-07-28 16:14 ` Stefan Monnier
2020-07-28 16:36 ` Matthew White
2020-07-28 18:06 ` Eli Zaretskii
2020-07-28 18:15 ` Matthew White
2020-07-24 17:07 ` Drew Adams
2020-07-24 17:07 ` Drew Adams
2020-07-24 16:43 ` Drew Adams
2020-07-24 5:31 ` Yuri Khan
2020-07-24 15:05 ` Stefan Monnier
2020-07-24 16:56 ` Noam Postavsky
2020-07-24 17:07 ` Drew Adams
2020-07-24 19:07 ` Karl Fogel
2020-07-25 10:46 ` Matthew White
2020-07-25 10:58 ` Eli Zaretskii
2020-07-25 15:33 ` Michael Albinus
2020-07-25 15:38 ` Eli Zaretskii
2020-07-25 15:56 ` Michael Albinus
2020-07-25 16:30 ` Eli Zaretskii
2020-07-25 16:33 ` Eli Zaretskii
2020-07-25 16:43 ` Michael Albinus
2020-07-25 16:55 ` Eli Zaretskii
2020-07-25 18:28 ` Matthew White
2020-07-25 18:54 ` Eli Zaretskii
2020-07-25 20:36 ` Karl Fogel
2020-07-25 21:14 ` Stefan Monnier
2020-07-25 22:40 ` Karl Fogel
2020-07-29 22:16 ` Karl Fogel
2020-07-31 2:58 ` Matthew White
2020-07-31 6:01 ` Karl Fogel
2020-08-02 22:13 ` Karl Fogel
2020-08-06 17:59 ` Matthew White
2020-08-07 1:10 ` Karl Fogel
2020-08-07 8:33 ` Matthew White
[not found] ` <jwveeojyxh1.fsf-monnier+emacs@gnu.org>
[not found] ` <87a6z715do.fsf@red-bean.com>
2020-08-07 17:05 ` Matthew White
2020-08-07 17:18 ` Eli Zaretskii
2020-08-08 8:23 ` Matthew White
2020-08-09 20:19 ` Karl Fogel
2020-08-10 5:41 ` Matthew White
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cd015f87-8253-490a-8e99-18842c00bc5e@default \
--to=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kfogel@red-bean.com \
--cc=mehw.is.me@inventati.org \
--cc=michael.albinus@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).