unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ivan Shmakov <ivan@siamics.net>
To: emacs-devel@gnu.org
Cc: , Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: [PATCH] Desktop mode saves mark-ring too verbosely
Date: Thu, 22 Jan 2015 08:20:39 +0000	[thread overview]
Message-ID: <87k30fql9k.fsf@violet.siamics.net> (raw)
In-Reply-To: <tHs2sJr0e2Gzp3ZnKllZVwFMbqABlBPugC3PJmzSpcR@local> (Kelly Dean's message of "Thu, 22 Jan 2015 05:43:47 +0000")

>>>>> Kelly Dean <kelly@prtime.org> writes:

[…]

 > @@ -628,6 +628,18 @@
 >    "When the desktop file was last modified to the knowledge of this Emacs.
 >  Used to detect desktop file conflicts.")

 > +(defvar desktop-var-serdes-funs

	I’d rather see it use the unabbreviated ‘-functions’ suffix.
	(Also, aren’t “serialization” and “deserialization” often
	referred to as “writing” and “reading” in the dialects of Lisp?)

 > +  (list (list
 > +	 'mark-ring
 > +	 (lambda (mr)
 > +	   (mapcar #'marker-position mr))
 > +	 (lambda (mr)
 > +	   (mapcar #'copy-marker mr))))
 > +  "Table of serdes functions for variables.

	It doesn’t look like a common abbreviation, so I guess
	“serializer, deserializer” should rather be spelled in full.
	(And even more so when it comes to the first line of a
	docstring.)

 > +Each record is a list of form: (var serializer deserializer).
 > +These records can be freely reordered, deleted, or new ones added.
 > +However, for compatibility, don't modify the functions for existing records.")
 > +

[…]

-- 
FSF associate member #7257  np. Machine Gun — Flotsam and Jetsam  … 230E 334A



  reply	other threads:[~2015-01-22  8:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-22  3:44 [PATCH] Desktop mode saves mark-ring too verbosely Kelly Dean
2013-11-23 13:40 ` Stefan Monnier
2015-01-21 12:11   ` Kelly Dean
2015-01-21 15:04     ` Stefan Monnier
2015-01-22  5:43       ` Kelly Dean
2015-01-22  8:20         ` Ivan Shmakov [this message]
2015-01-23 13:20           ` Kelly Dean
2015-01-23 14:09             ` Ivan Shmakov
2015-01-24  3:08             ` Stephen J. Turnbull
2015-01-24 23:30               ` Elisp terminology (was: Re: [PATCH] Desktop mode saves mark-ring too verbosely) Kelly Dean
2015-01-25  9:49                 ` Elisp terminology David Kastrup
  -- strict thread matches above, loose matches on Subject: below --
2015-01-23  2:59 Rant - Elisp terminology is deceptive Kelly Dean
2015-01-23 20:15 ` Stefan Monnier
2015-01-24  0:41   ` Kelly Dean
2015-01-24  0:48     ` Óscar Fuentes
2015-01-24  3:28     ` Stephen J. Turnbull
2015-01-24  8:51       ` Eli Zaretskii
2015-01-24 10:32         ` Kelly Dean
2015-01-24 11:26           ` Eli Zaretskii
2015-01-24 10:30       ` Kelly Dean
2015-01-24 11:03         ` David Kastrup
2015-01-24 23:24           ` Kelly Dean
2015-01-25  9:16             ` David Kastrup
2015-01-26  3:52               ` Kelly Dean
2015-01-26  8:28                 ` Thien-Thi Nguyen

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=87k30fql9k.fsf@violet.siamics.net \
    --to=ivan@siamics.net \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).