unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: tom.horsley@att.net (Thomas A. Horsley)
Cc: emacs-devel@gnu.org
Subject: Re: minibuffer-prompt-end badly named
Date: 13 Aug 2002 19:17:42 -0400	[thread overview]
Message-ID: <uu1lyl561.fsf@att.net> (raw)
In-Reply-To: <200208132247.g7DMlC607271@wijiji.santafe.edu>

>I will improve this area.
>
>    The function minibuffer-prompt-end (and all the other related functions
>    added for emacs21) are very badly documented.
>
>Could you give me a precise list of the functions that you think
>are badly documented?  I could afford to look at specific functions
>to try to improve their doc strings, but I'd rather not take the extra
>time to hunt for the right functions.

Upon further review, it may only be minibuffer-prompt-end that has the
really screwy doc string. The other functions right next to it all say they
must be used in the minibuffer, and in those cases, the rest of the doc
string is correct. I'd still like a function that actually does what the
current doc string for minibuffer-prompt-end claims to do :-).

The best I've come up with so far is:

(defun writable-point-min ()
"Return first writable position in current buffer."
   (let
      ( (rval (point-min)) )
      (if (get-text-property rval 'read-only)
         (setq rval (next-single-property-change rval 'read-only)) )
      rval ) )

--
>>==>> The *Best* political site <URL:http://www.vote-smart.org/> >>==+
      email: Tom.Horsley@worldnet.att.net icbm: Delray Beach, FL      |
<URL:http://home.att.net/~Tom.Horsley> Free Software and Politics <<==+

  reply	other threads:[~2002-08-13 23:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020813013725.QILD11162.mtiwmhc22.worldnet.att.net@SPIKE.att.net>
2002-08-13 22:47 ` minibuffer-prompt-end badly named Richard Stallman
2002-08-13 23:17   ` Thomas A. Horsley [this message]
2002-08-14 23:13     ` 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=uu1lyl561.fsf@att.net \
    --to=tom.horsley@att.net \
    --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).