git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [howto] Kernel hacker's guide to git, updated

From
AAAnton Altaparmakov <aia21@cam.ac.uk>
Date
Sep 29, 2005, 22:12 UTC
Message-ID
<Pine.LNX.4.60.0509292309470.17860@hermes-1.csi.cam.ac.uk>
In-Reply-To
<Pine.LNX.4.64.0509291451540.5362@g5.osdl.org>
On Thu, 29 Sep 2005, Linus Torvalds wrote:
Show 12 quoted lines
> On Thu, 29 Sep 2005, Dave Jones wrote:
> > What I find amusing is that it was a patch rejection mail from you
> > *years* back (circa 2000 iirc), telling me my pine corrupted whitespace,
> > that made me switch MUA ;-)
> > 
> > All these years later, and it's still buggered ?
> 
> Actually, it seems better. It seems to be buggered by default, but it used 
> to be that you had to actually recompile pine to make it behave. Now you 
> can just disable "strip-whitespace-before-send" and _enable_ 
> "quell-flowed-text" and those together seem to do the trick. No extra 
> patches or recompiles necessary.
Indeed.  I use those two options like that, too.  (-:
Show 10 quoted lines
> So there's progress. 
> 
> Of course, pico is still pico. Which I find a bit sad: my editor of choise 
> is still an improved version of uemacs, and pico actually comes from the 
> same uemacs history, but has different key-bindings for just enough keys 
> to be slightly confusing.
> 
> Still, that shared history means that I find pico a lot more to my taste 
> than just about any other emailer editor out there. It may have a few 
> differences, but it has more things in common..

Why don't you enable "enable-alternate-editor-implicitly" and set editor = "your-editor-of-choice" in the pine config? It is integrated in a quite seamless way.

Best regards,
	Anton
-- 
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net
WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/
Previous: Linus TorvaldsNext: Linus Torvalds
Message 18 of 40 in “[howto] Kernel hacker's guide to git, updated”
  1. Jeff GarzikSep 29, 2005
  2. David LeimbachSep 29, 2005
  3. Alberto PatinoSep 29, 2005
  4. David LeimbachSep 29, 2005
  5. Oliver NeukumSep 29, 2005
  6. Jon LoeligerSep 29, 2005
  7. Oliver NeukumSep 29, 2005
  8. Junio C HamanoSep 30, 2005
  9. Oliver NeukumSep 30, 2005
  10. Linus TorvaldsSep 30, 2005
  11. Dave JonesSep 29, 2005
  12. Anton AltaparmakovSep 29, 2005
  13. Dave JonesSep 29, 2005
  14. Linus TorvaldsSep 29, 2005
  15. Linus TorvaldsSep 29, 2005
  16. Dave JonesSep 29, 2005
  17. Linus TorvaldsSep 29, 2005
  18. Anton AltaparmakovSep 29, 2005
  19. Linus TorvaldsSep 29, 2005
  20. Anton AltaparmakovSep 29, 2005
  21. Junio C HamanoSep 29, 2005
  22. Johannes SchindelinSep 30, 2005
  23. Elfyn McBratneySep 29, 2005
  24. Linus TorvaldsSep 29, 2005
  25. Dave JonesSep 29, 2005
  26. Jeff GarzikSep 29, 2005
  27. Junio C HamanoSep 29, 2005
  28. Jeff GarzikSep 30, 2005
  29. Junio C HamanoSep 30, 2005
  30. Jeff GarzikSep 30, 2005
  31. Junio C HamanoOct 2, 2005
  32. Linus TorvaldsSep 30, 2005
  33. Junio C HamanoOct 1, 2005
  34. Oliver NeukumSep 30, 2005
  35. Jeff GarzikSep 30, 2005
  36. Alberto PatinoSep 30, 2005
  37. Erik MouwSep 30, 2005
  38. Jeff GarzikSep 30, 2005
  39. Francois RomieuSep 30, 2005
  40. Chuck LeverSep 29, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.