From: le@main.lekno.ws   
      
   Adam H. Kerman  wrote:   
   > Louis Epstein  wrote:   
   >>Adam H. Kerman  wrote:   
   >>>Louis Epstein  wrote:   
   >>>>Adam H. Kerman  wrote:   
   >>>>>Louis Epstein  wrote:   
   >>>>>>Adam H. Kerman  wrote:   
   >>>>>>>Louis Epstein  wrote:   
   >   
   >>>>>>>>>. . .   
   >   
   >>>>>>>>(Some "standards" infuriate me,such as being prevented from   
   >>>>>>>>quoting and commenting on someone's signature).   
   >   
   >>>>>>>Who said you can't comment on whatever you care to?   
   >   
   >>>>>>What I'm alluding to is the system whereby someone   
   >>>>>>precedes a signature with a line starting "-- "   
   >>>>>>and the newsreader thereby refuses to copy that or   
   >>>>>>anything after it when one is attempting to quote   
   >>>>>>the entire previous message and pare it down to what   
   >>>>>>one is responding to (which should treat the signature   
   >>>>>>as just as much fair game as previous text,IMO).   
   >   
   >>>>>trn is from the same era as tin. I have to delete the quoted .sigfile   
   >>>>>in followup manually.   
   >   
   >>>>>Copy-n-paste into your followup; manually add quote characters.   
   >   
   >>>>I don't use a mousey interface for my newsgroup reading.   
   >>>>I edit with pico.   
   >   
   >>>Shudder   
   >   
   >>>Long lines just run off the end of the screen!   
   >   
   >>Easily managed,a space/backspace chops the long lines,   
   >>repeat as needed.   
   >   
   >>>I use vim. I had been a long-time vi user.   
   >   
   >>I hate vi.   
   >>People say ed is worse but I haven't tried it.   
   >>Nor vim.   
   >   
   > ed was very basic.   
   >   
   >>For FreeBSD,/usr/ports/editors includes   
   >   
   > I know. The choices are amazing, aren't they. It's hard to convince   
   > people who don't understand that a newsreader or email client that calls   
   > on outside processes for certain functions, like the editor to use in   
   > the composer, are superior. They offer the user a choice. I'd hate to be   
   > stuck with a built-in editor in a GUI client which won't have the   
   > features I'm used to.   
      
   I get pico along with pine/alpine and I'm used to using   
   it with tin as well as for general composition of text   
   files.   
   GUI clients are not my style.   
      
   >>. . .   
   >   
   >>but tin as reader and pico as editor are what I'm most comfortable with.   
   >>I know trn has some abilities tin doesn't.   
   >   
   > trn threads. tin doesn't.   
      
   Tin presents a menu of threads,and can show you tree diagrams   
   of them...but I noted in the past when trn was able to show   
   me messages cleanly while tin was making mush of my .newsrc file.   
      
   -=-=-   
   The World Trade Center towers MUST rise again,   
   at least as tall as before...or terror has triumphed.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)