unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Subject: Re: desktop-missing-file-warning doc
Date: Sat, 13 May 2006 19:37:26 -0500 (CDT)	[thread overview]
Message-ID: <200605140037.k4E0bQwQ007255@jane.dms.auburn.edu> (raw)
In-Reply-To: <200605132236.k4DManEm007081@jane.dms.auburn.edu> (message from Luc Teirlinck on Sat, 13 May 2006 17:36:49 -0500 (CDT))

My CC to `Lars Hansen <lists@soem.dk>' in my previously sent message
(repeated below) somehow disappeared from the version that was sent to
me by emacs-devel.  I _did_ include it in the message I sent: it is in
the copy that got sent to my archive file.  I do not know what happened.

Anyway, if you reply, reply to this version.  I hope the CC comes
through correctly this time.

Original message:

`(elisp)Documentation Tips' states that the first line of a docstring
should not be wider than 67 characters.  The stated reason for that is
that otherwise it looks bad in apropos output.  But for defcustoms,
another reason is that if the first line is too long, it can look
really bad in a Custom buffer.  Just do `M-x customize-group desktop RET'
and look at desktop-missing-file-warning (assuming the default 80 chars
per line).

The first line of desktop-missing-file-warning is way too long:

If non-nil then `desktop-read' asks if a non-existent file should be recreated.

It has other problems.  If you just look at that first line, you get
the impression that if the value is nil, `desktop-read' creates the
file without asking, especially given the -warning at the end of the
name.  That is not what happens.  Since it seems impossible to
recreate a file that never existed, I guess that non-existent means
deleted.  The current first line uses the passive and there is another
convention to avoid that if it is unnecessary.

What about the following alternative first line, which reduces the
length of the first line to 60 characters, does not use passive and in
addition is also, I believe, clearer and easier to read.  I could
install if desired.

===File ~/desktop.el-diff===================================
*** desktop.el	13 May 2006 11:24:56 -0500	1.100
--- desktop.el	13 May 2006 16:56:13 -0500	
***************
*** 201,207 ****
    :version "22.1")
  
  (defcustom desktop-missing-file-warning nil
!   "*If non-nil then `desktop-read' asks if a non-existent file should be recreated.
  Also pause for a moment to display message about errors signaled in
  `desktop-buffer-mode-handlers'.
  
--- 201,207 ----
    :version "22.1")
  
  (defcustom desktop-missing-file-warning nil
!   "If non-nil,`desktop-read' offers to recreate a deleted file.
  Also pause for a moment to display message about errors signaled in
  `desktop-buffer-mode-handlers'.
  
============================================================

  reply	other threads:[~2006-05-14  0:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-13 22:36 desktop-missing-file-warning doc Luc Teirlinck
2006-05-14  0:37 ` Luc Teirlinck [this message]
2006-05-14  1:11   ` Luc Teirlinck
2006-05-14  1:16     ` Luc Teirlinck
2006-05-14  6:40   ` Lars Hansen
2006-05-14 18:10     ` Luc Teirlinck
2006-05-14 20:27       ` Lars Hansen
2006-05-14 23:28     ` Richard Stallman

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=200605140037.k4E0bQwQ007255@jane.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    /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).