I'm trying to run
xdotool type word then
xdotool key Return from Startup Aplications Preferences.
But if I use
;, xdotool evaluates it as continuation of input.
Long story short:
Use a script.
#! /bin/sh # With some window selection magic, or a sleep # if you want to do that manually. xdotool type word xdotool key Return
And put the path of the script in the
According to the
type Supports newlines and tabs (ASCII newline and tab). With respect to "COMMAND CHAINING", this command consumes the remainder of the arguments and types them. That is, no commands can chain after 'type'.
Command chaining via
& isn't possible, since that is shell syntax and Startup Applications doesn't support shell syntax. However, if all you wish to do is press Enter after typing something, there's a roundabout way to do so.
When it says "ASCII" newline, it doesn't mean a bare
\n. And command substitution (
xdotool type "$(printf '\n')", say) eats trailing newlines. Following this
xdotools forum post, I tried this:
xdotool type "$(printf 'date\n ')"
And it worked. But it only works if there is some character after the
\n, and this obviously leaves a trailing space, which would not be what you want.
I modified that to:
xdotool type "$(printf 'date\n\e ')"
And this works and leaves no trailing space. However, it might cause problems for those using Vi mode in their shell.
Thanks to @steeldriver's comments I figured out that this was due to me trying it out on the very terminal I was executing the commands on. Just a small gap between my pressing Enter and the
xdotool command was enough for a single newline to be registered correctly. Thus:
sleep 0.1; xdotool type $'date\n'
So either extending the line by quoting it:
xdotool type 'date '
or using the shell interpretation as @steeldriver suggested looks like the right option.
However, a script containing:
#! /bin/sh sleep 1 xdotool type date xdotool key Return
Exec field worked fine. Indeed, I always recommend using a script for complex commands in a desktop file.
You can have a script with
/usr/bin/xdotool in the shebang, but the manpage says "
script mode isn't fully fleshed out and may fall below your expectations", so I stuck to bash scripts.
I might have been seeing things, but in my first couple of tries, I had to put a (small) . That was an artifact of trying it out on the terminal that was executing the commands instead of another window.
sleep between the
Seems to me the application is not parsing multiple commands, abut treating it as a single command. As such make it a single command by wrapping it a shell call...
bash -c 'xdotool type date; xdotool key Return'
Now you can also do other shell things...
bash -c 'xdotool type "`date +"%Y-%m-%d_%T`"'
Note that the "date" command used in that last includes a newline! and "xdotool" will output it.
NOTE: if you are doing this as a keyboard macro I would also add a few more options to "xdotool" to make this work better...
bash -c 'xdotool type --clearmodifiers -delay 0 "`date +"%Y-%m-%d_%T`"'