thank you dana, I totally overlooked print -z, that's perfect for my use
case
in the meantime I also rediscovered about zle-line-init, which allow the
control of the next zle prompt and can get parameters from global variables.
To only allow it to act when the zle prompt is a PS1 one can set a global
variable in the precmd

Il giorno mer 13 giu 2018 alle ore 04:55 dana <dana@dana.is> ha scritto:

> On 12 Jun 2018, at 20:44, Pier Paolo Grassi <pierpaolog@gmail.com> wrote:
> >hello, I was wondering if it is somehow possibile to populate the command
> >line within the precmd function. What I am trying to achieve is: from a
> >normal function (not a zle widget) I would like to set some variable, to
> be
> >read in the precmd function where it is used to populate the next command
> >line and also set the cursor position.
>
> Maybe print's -z option would help, at least partially?
>
>   -z  Push the arguments onto the editing buffer stack, separated by
> spaces.
>
> Example:
>
>   % precmd_insert_args() {
>   >   # Check some variable, whatever
>   >   [[ $history[$((HISTCMD - 1))] == *bar* ]] && {
>   >     print 'Saw bar'
>   >     print -z : inserted args ''
>   >   }
>   >   return 0
>   > }
>   % precmd_functions+=( precmd_insert_args )
>   % : foo # Condition not met
>   % : bar
>   Saw bar
>   % : inserted args <CURSOR HERE>
>
> I say 'partially' because i'm not sure if you can affect the cursor
> position
> (besides inserting things in front of it, obv) from outside of a widget.
>
> dana
>
>

-- 
Pier Paolo Grassi
email: pierpaolog@gmail.com
linkedin: https://www.linkedin.com/in/pier-paolo-grassi-19300217
founder: https://www.meetup.com/it-IT/Machine-Learning-TO