Command-line arguments (Server): Difference between revisions

From FileZilla Wiki
Jump to navigationJump to search
(Undo revision 8266 by CodeSquid (talk))
(VDgPKZlenyBXeKeL)
Line 1: Line 1:
Ja nee stimmt, da gibt es keine neuen Kernel oder viel mehr merkt man von denen nur was, weil das aucimatosthe Update das gesamte System dem Erliegen nahe bringt. Wenn dann dem Antivirenprogramm noch einfe4llt, dass eigentlich ein Update nf6tig we4re, dann kf6nnen dem ersten Kaffee, denn der Start gedauert hat, getrost noch zwei Weitere folgen. ;-)Warum sollte man sich eigentlich den aktuelleren Kernel auf sein System laden? Ist es nicht meist so, dass eh nur neuere Features dazu gekommen sind, die man selbst vielleicht eher nicht so braucht? Mein Archlinux hat damit btw. keine Probleme.lGSchumbi
You just restored my sitnay ! I just converted from iTerm to iTerm2, and found that some of my nice alias commands didn't work. I checked I was in the same shell, logged in with the same switches. One specific issue I stripped down to find that a simple  ps -u' worked in iTerm but bombed in iTerm2 (and in Terminal). I was completely mystified, because surely they are both just dumb terminals running a simple unix command ? But I just checked and indeed iTerm login has COMMAND_MODE=legacy and iterm2 has COMMAND_MODE=unix2003 .

Revision as of 02:34, 23 August 2012

You just restored my sitnay ! I just converted from iTerm to iTerm2, and found that some of my nice alias commands didn't work. I checked I was in the same shell, logged in with the same switches. One specific issue I stripped down to find that a simple ps -u' worked in iTerm but bombed in iTerm2 (and in Terminal). I was completely mystified, because surely they are both just dumb terminals running a simple unix command ? But I just checked and indeed iTerm login has COMMAND_MODE=legacy and iterm2 has COMMAND_MODE=unix2003 .

Retrieved from "https://wiki.filezilla-project.org/wiki/index.php?title=Command-line_arguments_(Server)&oldid=18518"