all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: teirllm@dms.auburn.edu, emacs-devel@gnu.org
Subject: Re: Other potential problem with :format.
Date: Mon, 25 Aug 2003 21:38:30 -0400	[thread overview]
Message-ID: <E19rSn0-0005jZ-1j@fencepost.gnu.org> (raw)
In-Reply-To: <rjznhxevq7.fsf@zuse.dina.kvl.dk> (message from Per Abrahamsen on Mon, 25 Aug 2003 15:02:24 +0200)

    ! An editable fields must be surrounded by static text on both sides, that
    ! is, text that does not change in the lifetime of the widget.  If the
    ! field extend to the end of the line, the terminating line-feed character
    ! will count as the necessary static text on that end.  You will have to
    ! provide the static text before the field yourself.  The @code{:format}
    ! keyword is useful for that, if you give it a value of e.g.  @code{"Name:
    ! %v"} the "Name: " part will count as the static text.

It would be clearer with this small rewrite.

    ! An editable fields must be surrounded by static text on both
    ! sides, that is, text that does not change in the lifetime of the
    ! widget.  If the field extend to the end of the line, the
    ! terminating line-feed character will count as the necessary
    ! static text on that end, but you will have to provide the static
    ! text before the field yourself.  The @code{:format} keyword is
    ! useful for generating the static text; for instance, if you give
    ! it a value of @code{"Name: %v"}, the "Name: " part will count as
    ! the static text.

Can you install it?

  reply	other threads:[~2003-08-26  1:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-23 20:52 Other potential problem with :format Luc Teirlinck
2003-08-24 15:51 ` Per Abrahamsen
2003-08-25  3:30   ` Richard Stallman
2003-08-25 13:02     ` Per Abrahamsen
2003-08-26  1:38       ` Richard Stallman [this message]
2003-08-26  9:00         ` Per Abrahamsen
2003-08-26 13:12         ` Robert J. Chassell

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E19rSn0-0005jZ-1j@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.