Mit "Check Spelling" kann man eine Rechtschreibprüfung auslösen. Wichtig: unbekannte Wörter nur dann hinzufügen, wenn man sich 100%ig sicher ist, dass sie richtig geschrieben sind.
2025-05-04 | |||||
![]() |
BashFAQ/061 | 10:59 | ![]() |
ormaaj | bash's typeset -g is NOT zsh's -g! Now ksh93's -g has a bad backwards compatability blunder because I relied on this page not being wrong. Maybe we can still fix it with a rename but this is a problem |
![]() |
Bash Guide/Practices | 06:16 | ![]() |
StephaneChazelas [1-2] | #01 writing awk scripts is a bad recommendation #02 The point was that that syntax (including expr, backticks and missing quotes) is an ancient one that shouldn't be used any longer. |
2025-04-27 | |||||
![]() |
BashPitfalls | 09:37 | ![]() |
StephaneChazelas | few --s missing in arguments to cd in code meant to be "right" |
![]() |
Bash Programming/05 | 08:09 | ![]() |
StephaneChazelas | |
![]() |
BashFAQ/082 | 08:00 | ![]() |
StephaneChazelas [1-2] | #01 avoid potentially misleading users into thinking $() is a POSIX invention #02 what echo '\a' outputs depends on how bash was compiled and the environment |
2025-04-23 | |||||
![]() |
BashFAQ/028 | 20:13 | ![]() |
GreyCat [1] 81 [2-3] |
#01 Revert to revision 59. Pathnames separated by a space in a string variable are not correct. Breaks if $HOME contains a space for example. #02 (conf): rm extra "fi" #03 heneralize conf file code with for loop |
2025-04-20 | |||||
![]() |
BashFAQ/011 | 12:55 | ![]() |
StephaneChazelas | |
![]() |
BashFAQ/026 | 12:52 | ![]() |
StephaneChazelas | -v is perfectly POSIX, it wasn't in the original awk from the 70s, but neither was rand(). Separating statements with space isn't though. Needs ; or newline, awk can't take arbitrary file names |
2025-04-19 | |||||
![]() |
BashFAQ/005 | 17:16 | ![]() |
StephaneChazelas | |
![]() |
Process Substitution | 16:48 | ![]() |
StephaneChazelas | |
![]() |
Quotes | 16:19 | ![]() |
StephaneChazelas | |
![]() |
Bashism | 16:04 | ![]() |
StephaneChazelas | |
![]() |
BashFAQ/041 | 15:51 | ![]() |
StephaneChazelas [1-2] | |
![]() |
Reading Function Keys In Bash | 09:40 | ![]() |
StephaneChazelas [1-2] | #01 various improvements (I got bored after a while, so not exhaustive) |
![]() |
BashFAQ/071 | 09:07 | ![]() |
StephaneChazelas [1-2] | #01 various fixes and improvements |
![]() |
Bash Programming/03 | 07:42 | ![]() |
StephaneChazelas | pf65 update and various improvements. |
![]() |
Bash Programming/04 | 06:34 | ![]() |
StephaneChazelas | see pf65 update, no point in only considering the first argument. Can't split on whitespace as won't work if paths start with spaces. Need -files0-from to deal with paths that start with - |
2025-03-22 | |||||
![]() |
BashFAQ/006 | 09:32 | ![]() |
ormaaj | update nameref section to reflect current support status. |
2025-03-12 | |||||
![]() |
ParsingLs | 18:48 | ![]() |
GreyCat [1] 81 [2-5] |
#01 Every bad example MUST be labeled as such, WITHIN the example. Readers don't always look at context above or below the example. #02 Update for pho e display #03 Coreutils: adjust for phone display. Update wording as of 2025 (in reflect to 2016) #04 (Find): Adjust for phone display. Use neutral tone #05 Adjust for phone display. (Never do this): already in bold, adjust to use neutral tone in examples |
|
markiert ältere Seiten, die mindestens eine Sicherheitskopie haben (draufklicken für Autoren-Differenzanzeige) |
|
markiert Seiten, die seit Ihrem letzten Lesezeichen geändert wurden (draufklicken für eine Lesezeichen-Differenzanzeige) |
|
markiert Seiten, die seit Ihrem letzten Lesezeichen erzeugt worden sind und nicht danach geändert wurden |
|
markiert gelöschte Seiten |
|
markiert umbenannte Seiten |
|
Ein Editierkonflikt ist aufgetreten, bitte lösen Sie ihn, indem Sie beide Versionen der problematischen Absätze zusammenführen. |