unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lektu@terra.es>
Cc: emacs-devel@gnu.org
Subject: Re: Lowercase text after full stop on describe-variable
Date: Mon, 24 Jun 2002 18:29:40 +0200	[thread overview]
Message-ID: <20020624182600.F148.LEKTU@terra.es> (raw)
In-Reply-To: <200206241523.g5OFN8B02270@rum.cs.yale.edu>

And BTW, I'm wondering what's the reason you didn't include the
equivalent functionality for obsolescent functions, like in the simple
patch below (a slight modification of your describe-variable patch).

Is there some complication I'm missing?


                                                           /L/e/k/t/u




Index: help-fns.el
===================================================================
RCS file: /cvs/emacs/lisp/help-fns.el,v
retrieving revision 1.10
diff -u -2 -r1.10 help-fns.el
--- help-fns.el	23 Jun 2002 21:02:45 -0000	1.10
+++ help-fns.el	24 Jun 2002 16:25:40 -0000
@@ -278,4 +278,13 @@
 	     (princ arglist)
 	     (terpri))))
+    (let ((obsolete (get function 'byte-obsolete-info)))
+      (when obsolete
+        (terpri)
+        (princ "This function is obsolete")
+        (if (caddr obsolete) (princ (format " since %s" (caddr obsolete))))
+        (princ ".") (terpri)
+        (princ (if (stringp (car obsolete)) (car obsolete)
+                 (format "Use `%s' instead." (car obsolete))))
+        (terpri)))
     (let ((doc (documentation function)))
       (if doc

  parent reply	other threads:[~2002-06-24 16:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-24 13:49 Lowercase text after full stop on describe-variable Juanma Barranquero
2002-06-24 15:23 ` Stefan Monnier
2002-06-24 16:03   ` Juanma Barranquero
2002-06-24 16:29   ` Juanma Barranquero [this message]
2002-06-24 20:20     ` Stefan Monnier
2002-06-25  9:37       ` Juanma Barranquero
2002-06-25 14:20         ` Stefan Monnier
2002-06-25 17:04           ` Juanma Barranquero
2002-06-25 11:07     ` Richard Stallman
2002-06-27  8:54       ` Juanma Barranquero
2002-06-27 14:24         ` Stefan Monnier
2002-06-27 16:27           ` Juanma Barranquero
2002-06-27 16:44             ` Stefan Monnier
2002-06-27 19:14             ` Colin Walters
2002-06-28  6:41               ` Juanma Barranquero

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=20020624182600.F148.LEKTU@terra.es \
    --to=lektu@terra.es \
    --cc=emacs-devel@gnu.org \
    /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).