Re: [Fish-users] Unreadable!

2013-05-23 Thread Ben Franksen
Memnon Anon wrote: > For example, when I tried to rephrase the paragraph in my last mail, I > wasn't sure I quite knew what `token' actually meant. (If you search > through the manual, you'll see the term is never explained.) > > This may be due to my lacking english skills, or a definition may b

Re: [Fish-users] Unreadable!

2013-05-13 Thread Memnon Anon
Luciano ES writes: > [...] and I swear I am not joking. Hmm, sarcasm? Never. ;) Whatever, Bryan, this has been fixed by David Adam already 2 weeks ago in the git repository. -- AlienVault Unified Security Management

Re: [Fish-users] Unreadable!

2013-05-13 Thread Memnon Anon
Chris Wright writes: > 2013/5/12 Bryan Kilgallin > > What then is the purpose of documentation? I was trying to learn > this interface. But I found myself confounded by impenetrable > gobbledegook! > > That narrows it down, but it doesn't distinguish between sentence > structure

Re: [Fish-users] Unreadable!

2013-05-13 Thread Luciano ES
Bravo, Memnon. THAT is language that human beings can understand. And thank you for making me learn such a useful feature of the ridiculous fish shell. I wouldn't be able to decrypt the terse wording without your help. Note: I am a professional translator, paid to read-comprehend-translate-rew

Re: [Fish-users] Unreadable!

2013-05-13 Thread Memnon Anon
Martin Bähr writes: > On Sun, May 12, 2013 at 10:04:27PM +1000, Bryan Kilgallin wrote: >> "By pressing Alt-up and Alt-down, a history search is also performed, >> but instead of searching for a complete commandline, each commandline is >> tokenized into separate elements just like it would be b

Re: [Fish-users] Unreadable!

2013-05-12 Thread Chris Wright
2013/5/12 Bryan Kilgallin > Hi Chris: > > Thanks for writing. > > > What is your actual complaint? >> > > Here is a link to a document plain English check-list. > http://www.plainlanguage.gov/**howto/quickreference/**checklist.cfm

Re: [Fish-users] Unreadable!

2013-05-12 Thread Chris Wright
What is your actual complaint? "It has a high reading level" is true, but is the problem polysyllabic terminology that you don't understand? Is it sentence structure that takes you more time to parse than you think appropriate? Do you read it and parse it and then have trouble understanding how it

Re: [Fish-users] Unreadable!

2013-05-12 Thread Martin Bähr
On Sun, May 12, 2013 at 10:04:27PM +1000, Bryan Kilgallin wrote: > "By pressing Alt-up and Alt-down, a history search is also performed, > but instead of searching for a complete commandline, each commandline is > tokenized into separate elements just like it would be before execution, > and eac