From the terminal, I like launching my standard working applications ... gedit with my todo-list, firefox and chromium.
To save time, I (1) chain this command into one line, (2) silence all error messages from stderr and stdout with 2&>1 >/dev/null
and (3) background the processes with &
to regain a clean terminal:
gedit ~/Desktop/todo.txt 2&>1 > /dev/null & firefox 2&>1 > /dev/null & chromium-browser 2&>1 > /dev/null &
It seems to work fine except for one small detail. Gedit opens the todo file as well as a new textfile with the name 2. Are the pipes misplaced?
I tend to see
>/dev/null 2>&1
and not2>&1 >/dev/null
Then
>
is probably key here since the next options for gedit is (a) filename(s).Man page for gedit states for
filename(s)
:If I read this correctly: the 2 is seen as a filename since a space preceeds it. That would suggest you need the
>
to tell gedit that it is not a filename that comes next.I myself would create a script and have the commands on separate lines.
Quick answer:
The
-b
option putgedit
in background.Longer answer:
For a task like this one I'd put these applications in the startuo of your Desktop Environment.