unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: Using passing the tempo-template user input to my function?
Date: Tue, 26 Oct 2004 09:49:52 -0600	[thread overview]
Message-ID: <2u7a14F27qaajU1@uni-berlin.de> (raw)
In-Reply-To: <k_KdnQOP59eJ0ePcRVn-2Q@speakeasy.net>

Hattuari wrote:
 > I've tried all the ways I can come up with to pass the string 
returned from
 > querying the user to my own function.  I know the string is there, I can
 > paste it into the text at the point where I'm trying to paste a modified
 > version.
 >
 > This is an example of code that pastes the original user text:
 >
 > (tempo-define-template
 >  "array"
 >  '("typedef array<"
 >    (P "Data type: " data-type)
 >    ","
 >    (P "Number of components: 1 to 4 " data-order)
 >    "> Array" (s data-type)))
 > ;;

,----[ C-h f tempo-define-template RET ]
| tempo-define-template is a compiled Lisp function in `tempo'.
| (tempo-define-template NAME ELEMENTS &optional TAG DOCUMENTATION TAGLIST)
|
| Define a template.
| This function creates a template variable `tempo-template-NAME' and an
| interactive function `tempo-template-NAME' that inserts the template
| at the point.  The created function is returned.
...
| The elements in ELEMENTS can be of several types:
...
|  - The symbol 'p. This position is saved in `tempo-marks'.
...
|  - (p PROMPT <NAME> <NOINSERT>) If `tempo-interactive' is non-nil, the
|    user is prompted in the minbuffer with PROMPT for a string to be
|    inserted. If the optional parameter NAME is non-nil, the text is
|    saved for later insertion with the `s' tag. If there already is
|    something saved under NAME that value is used instead and no
|    prompting is made. If NOINSERT is provided and non-nil, nothing is
|    inserted, but text is still saved when a NAME is provided. For
|    clarity, the symbol 'noinsert should be used as argument.
|  - (P PROMPT <NAME> <NOINSERT>) Works just like the previous tag, but
|    forces tempo-interactive to be true.
...
|  - (s NAME) Inserts text previously read with the (p ..) construct.
|    Finds the insertion saved under NAME and inserts it. Acts like 'p
|    if tempo-interactive is nil.
...

If tempo-interactive is nil, perhaps you need to do something like

(let ((tempo-interactive t))
   (tempo-define-template ...))

which would also allow you to use (p ...) instead of (P ...) in your 
template.

-- 
Kevin Rodgers

  reply	other threads:[~2004-10-26 15:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-26 13:05 Using passing the tempo-template user input to my function? Hattuari
2004-10-26 15:49 ` Kevin Rodgers [this message]
2004-10-27  6:15   ` Hattuari
2004-10-27 16:59     ` Hattuari
2004-10-31 15:22       ` Kai Grossjohann
     [not found]       ` <mailman.6359.1099233079.2017.help-gnu-emacs@gnu.org>
2004-10-31 16:02         ` Hattuari
     [not found]           ` <mailman.6437.1099256821.2017.help-gnu-emacs@gnu.org>
2004-10-31 21:46             ` Hattuari
2004-10-31 21:56           ` Kai Grossjohann
2004-10-27 17:23 ` Vagn Johansen
2004-10-30 12:11   ` Hattuari

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=2u7a14F27qaajU1@uni-berlin.de \
    --to=ihs_4664@yahoo.com \
    /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.
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).