From: Per Abrahamsen <abraham@dina.kvl.dk>
Cc: teirllm@dms.auburn.edu, emacs-devel@gnu.org
Subject: Re: Other potential problem with :format.
Date: Mon, 25 Aug 2003 15:02:24 +0200 [thread overview]
Message-ID: <rjznhxevq7.fsf@zuse.dina.kvl.dk> (raw)
In-Reply-To: <E19r83O-0002Wu-Fb@fencepost.gnu.org> (Richard Stallman's message of "Sun, 24 Aug 2003 23:30:02 -0400")
Richard Stallman <rms@gnu.org> writes:
> Editable fields should in general be surrounded by static text, as
> they need the text to "anchor" themselves as we have little control of
> what happens inside the field.
>
> Could you please look at the manual and see if this could use being
> stated more clearly?
*** widget.texi.~1.19.~ Thu Aug 21 14:18:07 2003
--- widget.texi Mon Aug 25 15:01:36 2003
***************
*** 10,16 ****
@c %**end of header
@copying
! Copyright @copyright{} 2000, 2002 Free Software Foundation, Inc.
@quotation
Permission is granted to copy, distribute and/or modify this document
--- 10,16 ----
@c %**end of header
@copying
! Copyright @copyright{} 2000, 2002, 2003 Free Software Foundation, Inc.
@quotation
Permission is granted to copy, distribute and/or modify this document
***************
*** 211,217 ****
For example, capitalizing all text from the middle of one field to the
middle of another field is prohibited.
! Editing text fields are created by the @code{editable-field} widget.
The editing text fields are highlighted with the
@code{widget-field-face} face, making them easy to find.
--- 211,225 ----
For example, capitalizing all text from the middle of one field to the
middle of another field is prohibited.
! Editable text fields are created by the @code{editable-field} widget.
!
! 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.
The editing text fields are highlighted with the
@code{widget-field-face} face, making them easy to find.
next prev parent reply other threads:[~2003-08-25 13:02 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 [this message]
2003-08-26 1:38 ` Richard Stallman
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=rjznhxevq7.fsf@zuse.dina.kvl.dk \
--to=abraham@dina.kvl.dk \
--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.