{"thread":{"id":"177","subject":"[ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","startedAt":"2005-04-20T20:56:33Z","lastAt":"2005-04-25T11:27:22Z","messageCount":33,"participants":["Petr Baudis","Greg KH","Mike Taht","Randy.Dunlap","Joshua T. Corbin","Steven Cole","Linus Torvalds","Bryan Donlan","Daniel Jacobowitz","Sean","Dave Jones","Matthias Urlichs","Junio C Hamano","Ingo Molnar","Edgar Toernig","David A. Wheeler","Paul Jackson","Andrew Morton"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"1027","messageId":"20050420205633.GC19112@pasky.ji.cz","threadId":"177","inReplyTo":null,"subject":"[ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Petr Baudis","fromEmail":"pasky@ucw.cz","sentAt":"2005-04-20T20:56:33Z","receivedAt":"2005-04-20T20:56:33Z","isPatch":false,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"  Hello,\n\n  so I've \"released\" git-pasky-0.6.2 (my SCMish layer on top of Linus\nTorvalds' git tree history storage system), find it at the usual\n\n\thttp://pasky.or.cz/~pasky/dev/git/\n\n  git-pasky-0.6 has couple of big changes; mainly enhanced git diff,\ngit patch (to be renamed to cg mkpatch), enhanced git pull and\ncompletely reworked git merge - it now uses the git-core facilities for\nmerging, and does the merges in-tree. Plenty of smaller stuff, some\nbugfixes and some new bugs, and of course regular merging with Linus.\n\n  The most important change for current users is the objects database\nSHA1 keys change and (comparatively minor) directory cache format\nchange. This makes \"pulling up\" from older revisions rather difficult.\nLinus' instructions _should_ work for you too, basically (you should\nreplace cat .git/HEAD with cat .git/heads/* or equivalent - note that\nconvert-tree does not accept multiple arguments so you need to invoke it\nmultiple times), but I didn't test it well (I did it the lowlevel way\ncompletely since I needed to simultaneously merge with Linus).\n\n  But if you can't be bothered by this or fear touching stuff like that,\nand you do not have any local commits in your tree (it would be pretty\nstrange if you had and still fear), just fetch the tarball (which is\npreferrable than git init for me since it eats up _significantly_\nsmaller portion of my bandwidth).\n\n  I had to release git-pasky-0.6.1 since Linus changed the directory\ncache format during me releasing git-pasky-0.6. And git-pasky-0.6.2\nfixes gitmerge-file.sh script missing in the list of scripts for\ninstall.\n\n\n  So, now for the heads-up part. We will undergo at least two major\nchanges now. First, I'll probably make git-pasky to use the directory\ncache for the add/rm queues now that we have diff-cache.\n\n  Second, I've decided to straighten up the naming now that we still\nhave a chance. There will be no git-pasky-0.7, sorry. You'll get\ncogito-0.7 instead. I've decided for it since after some consideration\nhaving it named differently is the right thing (tm).\n\n  The short command version will change from 'git' to 'cg', which should\nbe shorter to type and free the 'git' command for possible eventual\nentry gate for the git commands (so that they are more\nnamespace-friendly, and it might make most sense anyway if we get fully\nlibgitized; but this is more of long-term ideas).\n\n  The usage changes:\n\n  cg patch -> cg mkpatch\t('patch' is the program which _applies_ it)\n  cg apply -> cg patch\t\t(analogically to diff | patch)\n\n  cg pull will now always only pull, never merge.\n\n  cg update will do pull + merge.\n\n  cg track will either just set the default for cg update if you pass it\nno parameters, or disappear altogether; I think it could default to the\n'origin' branch (or 'master' branch for non-master branches if no 'origin'\nbranch is around), and I'd rather set up some \"cg admin\" where you could\nset all this stuff - from this to e.g. the committer details [*1*]. You\nlikely don't need to change the default every day.\n\n  I must say that I'm pretty happy with the Cogito's command set\notherwise, though. I actually think it has now (almost?) all commands\nit needs, and it is not too likely that (many) more will be added -\nsimple means easy to use, which is Cogito's goal. Compare with\nthe command set of GNU arch clones. ;-)\n\n\n  [*1*] The committer details in .git would override the environemnt\nvariables to discourage people of trying to alter them based on\nwhatever, since that's not what they are supposed to do. They can always\njust change the .git stuff if they _really_ need to.\n\n\n  Comments welcomed, as well as new ideas. Persuading me to change what\nI sketched here will need some good arguments, though. ;-)\n\n  Thanks,\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\nC++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor\n"},{"id":"1028","messageId":"20050420210330.GD19112@pasky.ji.cz","threadId":"177","inReplyTo":"20050420205633.GC19112@pasky.ji.cz","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Petr Baudis","fromEmail":"pasky@ucw.cz","sentAt":"2005-04-20T21:03:30Z","receivedAt":"2005-04-20T21:03:30Z","isPatch":false,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"Dear diary, on Wed, Apr 20, 2005 at 10:56:33PM CEST, I got a letter\nwhere Petr Baudis <pasky@ucw.cz> told me that...\n>   cg pull will now always only pull, never merge.\n> \n>   cg update will do pull + merge.\n\nNote that what you will probably do _most_ by far is cg update.\nYou generally do cg pull only when you want to make sure you have the\nlatest and greatest when doing some cg diff or whatever, or on your\nnotebook when getting on an airplane. And you do direct cg merge generally\nonly on the airplane.\n\nI also forgot one last usage change:\n\n  cg fork BNAME BRANCH_DIR [COMMIT_ID]\n  ->\n  cg fork BRANCH_DIR [BNAME] [COMMIT_ID]\n\nThis will bring its usage in sync to both cg export and cg tag.\nThe branch name will also default to the last element in the\nBRANCH_DIR path (that annoyed me a lot, basically writing a thing\ntwo times at single line).\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\nC++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor\n"},{"id":"1030","messageId":"20050420211919.GA20129@kroah.com","threadId":"177","inReplyTo":"20050420205633.GC19112@pasky.ji.cz","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Greg KH","fromEmail":"greg@kroah.com","sentAt":"2005-04-20T21:19:19Z","receivedAt":"2005-04-20T21:19:19Z","isPatch":false,"sender":{"key":"greg@kroah.com","avatar":"https://gravatar.com/avatar/5bb5aa0cc2e01c00ec899d11130c07796bc186e465bae57bc34873b13b72c7c8?d=mp&s=160"},"body":"On Wed, Apr 20, 2005 at 10:56:33PM +0200, Petr Baudis wrote:\n>   The short command version will change from 'git' to 'cg', which should\n> be shorter to type and free the 'git' command for possible eventual\n> entry gate for the git commands (so that they are more\n> namespace-friendly, and it might make most sense anyway if we get fully\n> libgitized; but this is more of long-term ideas).\n\nHm, but there already is a 'cg' program out there:\n\thttp://uzix.org/cgvg.html\nI use it every day :(\n\nHow about 'cog' instead?\n\nOr I can just rename my local copy of cg and try to retrain my\nfingers...\n\nthanks,\n\ngreg k-h\n"},{"id":"1036","messageId":"4266CED2.60806@timesys.com","threadId":"177","inReplyTo":"20050420211919.GA20129@kroah.com","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Mike Taht","fromEmail":"mike.taht@timesys.com","sentAt":"2005-04-20T21:51:14Z","receivedAt":"2005-04-20T21:51:14Z","isPatch":false,"sender":{"key":"mike.taht@timesys.com","avatar":null},"body":"\nI keep thinking perversely that we need something as obtuse as possible\nin the unix tradition, but easy to type... git requires that the fingers\nmove off the home row...\n\nhow about \"asdf\" or \"jkl\"?  :)\n\ncg is singularly uncomfortable to type. I think that's why it isn't \ncommonly used.....\n\nGreg KH wrote:\n> On Wed, Apr 20, 2005 at 10:56:33PM +0200, Petr Baudis wrote:\n> \n>>  The short command version will change from 'git' to 'cg', which should\n>>be shorter to type and free the 'git' command for possible eventual\n>>entry gate for the git commands (so that they are more\n>>namespace-friendly, and it might make most sense anyway if we get fully\n>>libgitized; but this is more of long-term ideas).\n> \n> \n> Hm, but there already is a 'cg' program out there:\n> \thttp://uzix.org/cgvg.html\n> I use it every day :(\n> \n> How about 'cog' instead?\n> \n> Or I can just rename my local copy of cg and try to retrain my\n> fingers...\n> \n> thanks,\n> \n> greg k-h\n> -\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at  http://vger.kernel.org/majordomo-info.html\n\n\n-- \n\nMike Taht\n\n\n   \"New systems generate new problems.\"\n"},{"id":"1037","messageId":"20050420215117.GJ19112@pasky.ji.cz","threadId":"177","inReplyTo":"20050420211919.GA20129@kroah.com","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Petr Baudis","fromEmail":"pasky@ucw.cz","sentAt":"2005-04-20T21:51:18Z","receivedAt":"2005-04-20T21:51:18Z","isPatch":false,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"Dear diary, on Wed, Apr 20, 2005 at 11:19:19PM CEST, I got a letter\nwhere Greg KH <greg@kroah.com> told me that...\n> On Wed, Apr 20, 2005 at 10:56:33PM +0200, Petr Baudis wrote:\n> >   The short command version will change from 'git' to 'cg', which should\n> > be shorter to type and free the 'git' command for possible eventual\n> > entry gate for the git commands (so that they are more\n> > namespace-friendly, and it might make most sense anyway if we get fully\n> > libgitized; but this is more of long-term ideas).\n> \n> Hm, but there already is a 'cg' program out there:\n> \thttp://uzix.org/cgvg.html\n> I use it every day :(\n> \n> How about 'cog' instead?\n\nGrm. Cg is also name of some scary NVidia thing, and cog is GNOME\nConfigurator. CGT are Chimera Grid Tools, but I think we can clash\nwith those - at least *I* wouldn't mind. ;-)\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\nC++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor\n"},{"id":"1038","messageId":"20050420145419.6412414f.rddunlap@osdl.org","threadId":"177","inReplyTo":"20050420215117.GJ19112@pasky.ji.cz","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Randy.Dunlap","fromEmail":"rddunlap@osdl.org","sentAt":"2005-04-20T21:54:19Z","receivedAt":"2005-04-20T21:54:19Z","isPatch":false,"sender":{"key":"rddunlap@osdl.org","avatar":null},"body":"On Wed, 20 Apr 2005 23:51:18 +0200 Petr Baudis wrote:\n\n| Dear diary, on Wed, Apr 20, 2005 at 11:19:19PM CEST, I got a letter\n| where Greg KH <greg@kroah.com> told me that...\n| > On Wed, Apr 20, 2005 at 10:56:33PM +0200, Petr Baudis wrote:\n| > >   The short command version will change from 'git' to 'cg', which should\n| > > be shorter to type and free the 'git' command for possible eventual\n| > > entry gate for the git commands (so that they are more\n| > > namespace-friendly, and it might make most sense anyway if we get fully\n| > > libgitized; but this is more of long-term ideas).\n| > \n| > Hm, but there already is a 'cg' program out there:\n| > \thttp://uzix.org/cgvg.html\n| > I use it every day :(\n| > \n| > How about 'cog' instead?\n| \n| Grm. Cg is also name of some scary NVidia thing, and cog is GNOME\n| Configurator. CGT are Chimera Grid Tools, but I think we can clash\n| with those - at least *I* wouldn't mind. ;-)\n\nI'd rather see you go back to 'tig'...\n\nis there a tig out there?\n\n---\n~Randy\n"},{"id":"1039","messageId":"200504201758.18456.jcorbin@wunjo.org","threadId":"177","inReplyTo":"4266CED2.60806@timesys.com","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Joshua T. Corbin","fromEmail":"jcorbin@wunjo.org","sentAt":"2005-04-20T21:58:18Z","receivedAt":"2005-04-20T21:58:18Z","isPatch":false,"sender":{"key":"jcorbin@wunjo.org","avatar":null},"body":"On 20 April 2005 17:51, Mike Taht wrote:\n> I keep thinking perversely that we need something as obtuse as possible\n> in the unix tradition, but easy to type... git requires that the fingers\n> move off the home row...\n>\n> how about \"asdf\" or \"jkl\"?  :)\n>\n> cg is singularly uncomfortable to type. I think that's why it isn't\n> commonly used.....\nHmm...got to disagree, cg is perfectly comfortable to type here on my dvorak, \nwhilst asdf ad jkl are uncomfortable deviations accross the board ;-)\n\n-- \nRegards,\nJoshua T. Corbin <jcorbin@wunjo.org>\n"},{"id":"1041","messageId":"4266D297.20506@mesatop.com","threadId":"177","inReplyTo":"20050420145419.6412414f.rddunlap@osdl.org","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Steven Cole","fromEmail":"elenstev@mesatop.com","sentAt":"2005-04-20T22:07:19Z","receivedAt":"2005-04-20T22:07:19Z","isPatch":false,"sender":{"key":"elenstev@mesatop.com","avatar":null},"body":"Randy.Dunlap wrote:\n> On Wed, 20 Apr 2005 23:51:18 +0200 Petr Baudis wrote:\n> \n> | Dear diary, on Wed, Apr 20, 2005 at 11:19:19PM CEST, I got a letter\n> | where Greg KH <greg@kroah.com> told me that...\n> | > On Wed, Apr 20, 2005 at 10:56:33PM +0200, Petr Baudis wrote:\n> | > >   The short command version will change from 'git' to 'cg', which should\n> | > > be shorter to type and free the 'git' command for possible eventual\n> | > > entry gate for the git commands (so that they are more\n> | > > namespace-friendly, and it might make most sense anyway if we get fully\n> | > > libgitized; but this is more of long-term ideas).\n> | > \n> | > Hm, but there already is a 'cg' program out there:\n> | > \thttp://uzix.org/cgvg.html\n> | > I use it every day :(\n> | > \n> | > How about 'cog' instead?\n> | \n> | Grm. Cg is also name of some scary NVidia thing, and cog is GNOME\n> | Configurator. CGT are Chimera Grid Tools, but I think we can clash\n> | with those - at least *I* wouldn't mind. ;-)\n> \n> I'd rather see you go back to 'tig'...\n> \n> is there a tig out there?\n> \n> ---\n> ~Randy\n\nSince I was the one who came up with the \"cogito\" name, I'll suggest\nsome alternatives if cogito is unworkable.  This was posted once before,\nmostly as a joke, but here goes.\n\nagitato  ag     Since Beethoven's \"Moonlight\" 3rd mvmt is Presto agitato\n                 and very, very fast, just like git.\n\nlegit le or lg  Since git is GPLv2, it's now legit.\n\n\nSteven\n"},{"id":"1042","messageId":"Pine.LNX.4.58.0504201503050.6467@ppc970.osdl.org","threadId":"177","inReplyTo":"20050420215117.GJ19112@pasky.ji.cz","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Linus Torvalds","fromEmail":"torvalds@osdl.org","sentAt":"2005-04-20T22:09:06Z","receivedAt":"2005-04-20T22:09:06Z","isPatch":false,"sender":{"key":"torvalds@linux-foundation.org","avatar":"https://avatars.githubusercontent.com/u/1024025?v=4"},"body":"\n\nOn Wed, 20 Apr 2005, Petr Baudis wrote:\n> \n> Grm. Cg is also name of some scary NVidia thing, and cog is GNOME\n> Configurator. CGT are Chimera Grid Tools, but I think we can clash\n> with those - at least *I* wouldn't mind. ;-)\n\nI realize that there is probably a law that there has to be a space, but I \nactually personally use tab-completion all the time, and in many ways \nprefer a name that can be completed without having to play games with \nmagic bash completion files.\n\nSo how about using a dash instead of a space, and making things be\n\n\tcg-pull\n\tcg-update\n\netc? You can link them all to the same script if you don't like having \nmultiple scripts, and just match with\n\n\tcase \"$0\" in\n\t*-pull)\n\t\t...\n\t\t;;\n\t*-update)\n\t\t...\n\t\t;;\n\nor something.\n\nYeah, yeah, it looks different from \"cvs update\", but dammit, wouldn't it \nbe cool to just write \"cg-<tab><tab>\" and see the command choices? Or \n\"cg-up<tab>\" and get cg-update done for you..\n\nJust because rcs/cvs/everybody-and-his-dog thinks it is cool to have a \nspace there and have different meaning for flags depending on whether they \nare before the command or after the command doesn't mean that they are \nnecessarily right..\n\nJust an idea,\n\n\t\tLinus\n"},{"id":"1046","messageId":"20050420222815.GM19112@pasky.ji.cz","threadId":"177","inReplyTo":"Pine.LNX.4.58.0504201503050.6467@ppc970.osdl.org","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Petr Baudis","fromEmail":"pasky@ucw.cz","sentAt":"2005-04-20T22:28:15Z","receivedAt":"2005-04-20T22:28:15Z","isPatch":false,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"Dear diary, on Thu, Apr 21, 2005 at 12:09:06AM CEST, I got a letter\nwhere Linus Torvalds <torvalds@osdl.org> told me that...\n> Yeah, yeah, it looks different from \"cvs update\", but dammit, wouldn't it \n> be cool to just write \"cg-<tab><tab>\" and see the command choices? Or \n> \"cg-up<tab>\" and get cg-update done for you..\n\nI like this idea! :-) I guess that is in fact exactly what I have been\nlooking for, and (as probably apparent from the current git-pasky\nstructure) I prefer to have the scripts separated anyway.\n\nI think I will go for it. I also thought about having this _and_ a 'cg'\ncommand which would act as a completely dumb multiplexer, but I decided\nto toss that idea since it would only create usage ambiguity and other\nproblems on the long run.\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\nC++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor\n"},{"id":"1054","messageId":"20050420230457.GA23415@kroah.com","threadId":"177","inReplyTo":"20050420222815.GM19112@pasky.ji.cz","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Greg KH","fromEmail":"greg@kroah.com","sentAt":"2005-04-20T23:04:58Z","receivedAt":"2005-04-20T23:04:58Z","isPatch":false,"sender":{"key":"greg@kroah.com","avatar":"https://gravatar.com/avatar/5bb5aa0cc2e01c00ec899d11130c07796bc186e465bae57bc34873b13b72c7c8?d=mp&s=160"},"body":"On Thu, Apr 21, 2005 at 12:28:15AM +0200, Petr Baudis wrote:\n> Dear diary, on Thu, Apr 21, 2005 at 12:09:06AM CEST, I got a letter\n> where Linus Torvalds <torvalds@osdl.org> told me that...\n> > Yeah, yeah, it looks different from \"cvs update\", but dammit, wouldn't it \n> > be cool to just write \"cg-<tab><tab>\" and see the command choices? Or \n> > \"cg-up<tab>\" and get cg-update done for you..\n> \n> I like this idea! :-) I guess that is in fact exactly what I have been\n> looking for, and (as probably apparent from the current git-pasky\n> structure) I prefer to have the scripts separated anyway.\n\nI agree, it would solve the issue with 'cg' being overloaded, and I too\nlike the <tab><tab> completion idea.\n\nthanks,\n\ngreg k-h\n"},{"id":"1065","messageId":"Pine.LNX.4.58.0504201710500.2344@ppc970.osdl.org","threadId":"177","inReplyTo":"20050420222815.GM19112@pasky.ji.cz","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Linus Torvalds","fromEmail":"torvalds@osdl.org","sentAt":"2005-04-21T00:14:03Z","receivedAt":"2005-04-21T00:14:03Z","isPatch":false,"sender":{"key":"torvalds@linux-foundation.org","avatar":"https://avatars.githubusercontent.com/u/1024025?v=4"},"body":"\n\nPasky,\n what do you think about this change to \"git log\"?\n\nIt makes it a _lot_ easier to parse the result, as it indents all the\ncomments by two spaces, meaning that the header is clearly marked, and you\ncan then do various 'sed'/'grep' things with nice normal regular\nexpressions like '^parent' without having to worry about there being a \nline that starts with \"parent\" in the free-form part..\n\nI also think the end result is more readable from a human standpoint, with \nindentation as the way to distinguish the headers from the commentary, \nand less ugly ASCII barfic's with \"------\" etc.\n\nI'm doing a 2.6.12-rc3 release, so I care more than usual about the \nchangelog ;)\n\n\t\tLinus\n\n---\ngitlog.sh: a496a864f9586e47a4d7bd3ae0af0b3e07b7deb8\n--- a/gitlog.sh\n+++ b/gitlog.sh\n@@ -28,7 +28,7 @@ rev-tree $base | sort -rn | while read t\n \t\t\t\tfi\n \t\t\t\t;;\n \t\t\t\"\")\n-\t\t\t\techo; cat\n+\t\t\t\techo; sed 's/^/  /'\n \t\t\t\t;;\n \t\t\t*)\n \t\t\t\techo $key $rest\n@@ -36,5 +36,5 @@ rev-tree $base | sort -rn | while read t\n \t\t\tesac\n \n \t\tdone\n-\techo -e \"\\n--------------------------\"\n+\techo\n done\n"},{"id":"1074","messageId":"Pine.LNX.4.58.0504201809170.2344@ppc970.osdl.org","threadId":"177","inReplyTo":"Pine.LNX.4.58.0504201710500.2344@ppc970.osdl.org","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Linus Torvalds","fromEmail":"torvalds@osdl.org","sentAt":"2005-04-21T01:12:34Z","receivedAt":"2005-04-21T01:12:34Z","isPatch":false,"sender":{"key":"torvalds@linux-foundation.org","avatar":"https://avatars.githubusercontent.com/u/1024025?v=4"},"body":"\n\nOn Wed, 20 Apr 2005, Linus Torvalds wrote:\n> \n> Pasky,\n>  what do you think about this change to \"git log\"?\n\nHere's a slightly updated version.\n\nIt's identical to the previous one, except that it also feeds the result \nthrough \"| ${PAGER:-less}\" which makes it a lot more useful, in my \nopinion.\n\nIf you redirect the output to a non-tty, both \"less\" and \"more\" do the \nright thing and just feed the output straight through. But if the output \nis a tty, this makes \"git log\" a lot more friendly than a quickly \nscrolling mess..\n\n\t\tLinus\n\n----\ngitlog.sh: a496a864f9586e47a4d7bd3ae0af0b3e07b7deb8\n--- a/gitlog.sh\n+++ b/gitlog.sh\n@@ -28,7 +28,7 @@ rev-tree $base | sort -rn | while read t\n \t\t\t\tfi\n \t\t\t\t;;\n \t\t\t\"\")\n-\t\t\t\techo; cat\n+\t\t\t\techo; sed 's/^/  /'\n \t\t\t\t;;\n \t\t\t*)\n \t\t\t\techo $key $rest\n@@ -36,5 +36,5 @@ rev-tree $base | sort -rn | while read t\n \t\t\tesac\n \n \t\tdone\n-\techo -e \"\\n--------------------------\"\n-done\n+\techo\n+done | ${PAGER:-less}\n"},{"id":"1086","messageId":"2577.10.10.10.24.1114051520.squirrel@linux1","threadId":"177","inReplyTo":"20050421033526.GA9404@nevyn.them.org","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Sean","fromEmail":"seanlkml@sympatico.ca","sentAt":"2005-04-21T02:45:20Z","receivedAt":"2005-04-21T02:45:20Z","isPatch":false,"sender":{"key":"seanlkml@sympatico.ca","avatar":"https://gravatar.com/avatar/f92923f54fc08c401fc59b71829d4b89e9b8087fbba45ff87c82e6a83aee02ae?d=mp&s=160"},"body":"On Wed, April 20, 2005 11:35 pm, Daniel Jacobowitz said:\n\n> My logic: it's a lot more intuitive to say \"cg-log | less\" to get\npaginated output than it is to say \"cg-log | cat\" to get unpaginated\noutput.\n>\n\nDaniel,\n\nAll you'd have to do is:\n\n$ export PAGER=cat\n\nto get the behavior you want.\n\nSean\n\n\n\n\n"},{"id":"1092","messageId":"pan.2005.04.21.02.48.19.802122@smurf.noris.de","threadId":"177","inReplyTo":"Pine.LNX.4.58.0504201503050.6467@ppc970.osdl.org","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Matthias Urlichs","fromEmail":"smurf@smurf.noris.de","sentAt":"2005-04-21T02:48:19Z","receivedAt":"2005-04-21T02:48:19Z","isPatch":false,"sender":{"key":"matthias@urlichs.de","avatar":"https://gravatar.com/avatar/2708905af227313eba6f2b2ae0f7d0259b5ac5d71baef58fe5a13c699ce0bbf0?d=mp&s=160"},"body":"Linus Torvalds wrote:\n\n> I realize that there is probably a law that there has to be a space, but I \n> actually personally use tab-completion all the time\n\nYou can actually teach bash3 to do that (yes, with space).\n\nIn general, though, I tend to agree -- dashes work with more shells and\navoid namespace collisions.\n\n-- \nMatthias Urlichs\n\n"},{"id":"1081","messageId":"u6hjj2-jl9.ln1@bd-home-comp.no-ip.org","threadId":"177","inReplyTo":"20050420205633.GC19112@pasky.ji.cz","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Bryan Donlan","fromEmail":"bdonlan@bd.beginyourfear.com","sentAt":"2005-04-21T02:53:33Z","receivedAt":"2005-04-21T02:53:33Z","isPatch":false,"sender":{"key":"bdonlan@bd.beginyourfear.com","avatar":null},"body":"-----BEGIN PGP SIGNED MESSAGE-----\nHash: RIPEMD160\n\nPetr Baudis wrote:\n|   Hello,\n|\n|   so I've \"released\" git-pasky-0.6.2 (my SCMish layer on top of Linus\n| Torvalds' git tree history storage system), find it at the usual\n|\n| \thttp://pasky.or.cz/~pasky/dev/git/\n\nWhen I run `git pull', I get:\n\nTree change:\n55f9d5042603fff4ddfaf4e5f004d2995286d6d3:7a4c67965de68ae7bc7aa1fde33f8eb9d8114697\n+100644\tblob\t8186a561108d3c62625614272bd5e2f7d5826b4b\tREADME.reference\n*100755->100755\tblob\n5f23301eb97a0fadd505a6e9cc851e98741a512a->bf277135908ee7c6b7d6ad330d1ce183b9bb411f\ngit\n*100755->100755\tblob\na78cf8ccab98861ef7aecb4cb5a79e47d3a84b67->74b4083d67eda87d88a6f92c6c66877bba8bda8a\ngitcancel.sh\nTracked branch, applying changes...\nFast-forwarding 55f9d5042603fff4ddfaf4e5f004d2995286d6d3 ->\n7a4c67965de68ae7bc7aa1fde33f8eb9d8114697\n\ton top of 55f9d5042603fff4ddfaf4e5f004d2995286d6d3...\npatch: **** Only garbage was found in the patch input.\n\nI'm on debian testing, patch 2.5.9. It seems to apply the changes\ndespite this error.\n\nThanks,\n\nBryan Donlan\n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v1.4.0 (GNU/Linux)\nComment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org\n\niQIVAwUBQmcVqXhF4rlE0/81AQPNdA//fmL+O3amch3WUfYLZroSNarto/jcQ8WE\nNAwthoT+nPkvUcrgoPVPvuJKmKlemBLGqJhz5raOgL8Cu09ttnHh9zi9fz/XD2uR\nFFJ603xJDBqHGAG3FVS9EHaTdIFq7kSgVKn90BGdR/gxYR5oCt9DHbOzpI9S0DC5\no580CvtMHRfN1mUwhmxt8oU1E5obRvHlwQ2R4kVl90DBmPNRNXMiWziKjaVyKVng\nIXR2ERfCb1HurZfoOlcmhw0Aod7sJpjubf/tm9CDdRIkMdKkeuKBqWbanzHJTlJG\n2GOH2Q0CNp1HscFO+DKsCPBMa8zLAPuN0AF//o8URzXElwFiAfQNMjK8hOFVBI2y\n6OR/WUvwlXUs47+9QJX7mLTjTJIgcHsxZF9amX37jXKiL5iZyDUJD9wxcFL6A1ut\neVntC36Fp6yx8zROAex0hNx68LHTILUh5bDi3N9gTnpplWpCn02GNkQi18GQLk4Z\nY34WipxwGImbJooGveHh8nH6v/6V4fOy1SaxaV5q4EL563wGrRlIZ9/POgWeJoas\nD5S7aJgXCw0GLTJFZCEDORUTCv73HgxR7zSlyqup2qR0Tjqv/JWTCfqCSRLJ8Ktc\nPVKf2Alx6ycVFbh9XhQUKWT4tLm1KywpTUvZe+K0DMfw28dbRREnRyFVqbId8JmX\nLJgbHTVxRCs=\n=Fx+f\n-----END PGP SIGNATURE-----\n\n"},{"id":"1085","messageId":"20050421033526.GA9404@nevyn.them.org","threadId":"177","inReplyTo":"Pine.LNX.4.58.0504201809170.2344@ppc970.osdl.org","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Daniel Jacobowitz","fromEmail":"dan@debian.org","sentAt":"2005-04-21T03:35:27Z","receivedAt":"2005-04-21T03:35:27Z","isPatch":false,"sender":{"key":"dan@debian.org","avatar":null},"body":"On Wed, Apr 20, 2005 at 06:12:34PM -0700, Linus Torvalds wrote:\n> Here's a slightly updated version.\n> \n> It's identical to the previous one, except that it also feeds the result \n> through \"| ${PAGER:-less}\" which makes it a lot more useful, in my \n> opinion.\n> \n> If you redirect the output to a non-tty, both \"less\" and \"more\" do the \n> right thing and just feed the output straight through. But if the output \n> is a tty, this makes \"git log\" a lot more friendly than a quickly \n> scrolling mess..\n\nPersonally, I'd rather it didn't do this; bk help does the same thing,\nand it drives me crazy.  I guess you have /usr/bin/man for a precedent,\nthough :-)\n\nMy logic: it's a lot more intuitive to say \"cg-log | less\" to get\npaginated output than it is to say \"cg-log | cat\" to get unpaginated\noutput.\n\n-- \nDaniel Jacobowitz\nCodeSourcery, LLC\n"},{"id":"1087","messageId":"Pine.LNX.4.58.0504202056310.2344@ppc970.osdl.org","threadId":"177","inReplyTo":"20050421033526.GA9404@nevyn.them.org","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Linus Torvalds","fromEmail":"torvalds@osdl.org","sentAt":"2005-04-21T04:00:44Z","receivedAt":"2005-04-21T04:00:44Z","isPatch":false,"sender":{"key":"torvalds@linux-foundation.org","avatar":"https://avatars.githubusercontent.com/u/1024025?v=4"},"body":"\n\nOn Wed, 20 Apr 2005, Daniel Jacobowitz wrote:\n> \n> My logic: it's a lot more intuitive to say \"cg-log | less\" to get\n> paginated output than it is to say \"cg-log | cat\" to get unpaginated\n> output.\n\nI disagree.\n\nThere is _never_ any valid situation where you do \"cg-log\" with \nunpaginated output to a tty.\n\nIn _any_ real system you'll be getting thousands of lines of output. \nPossibly millions. unpaginated? What the hell are you talking about?\n\nAnd as I pointed out, if the output is not a tty, then both less and more\nautomatically turn into cat, so there's no difference. This change _only_\ntriggers for a tty, and I dare you to show a single relevant project where \nit's ok to scroll thousands of lines.\n\nEven git-pasky, which is just a two-week-old project right now outputs \n4338 lines of output to \"git log\". \n\nUnpaginated? You must be kidding.\n\n(But if you are _that_ fast a reader, then hey, use \"PAGER=cat\", and \nyou'll find yourself happy).\n\n\t\tLinus\n"},{"id":"1089","messageId":"20050421042248.GA16002@redhat.com","threadId":"177","inReplyTo":"Pine.LNX.4.58.0504202056310.2344@ppc970.osdl.org","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Dave Jones","fromEmail":"davej@redhat.com","sentAt":"2005-04-21T04:22:48Z","receivedAt":"2005-04-21T04:22:48Z","isPatch":false,"sender":{"key":"davej@redhat.com","avatar":null},"body":"On Wed, Apr 20, 2005 at 09:00:44PM -0700, Linus Torvalds wrote:\n \n > > My logic: it's a lot more intuitive to say \"cg-log | less\" to get\n > > paginated output than it is to say \"cg-log | cat\" to get unpaginated\n > > output.\n > I disagree.\n > \n > There is _never_ any valid situation where you do \"cg-log\" with \n > unpaginated output to a tty.\n > \n > In _any_ real system you'll be getting thousands of lines of output. \n > Possibly millions. unpaginated? What the hell are you talking about?\n > \n > And as I pointed out, if the output is not a tty, then both less and more\n > automatically turn into cat, so there's no difference. This change _only_\n > triggers for a tty, and I dare you to show a single relevant project where \n > it's ok to scroll thousands of lines.\n > \n > Even git-pasky, which is just a two-week-old project right now outputs \n > 4338 lines of output to \"git log\". \n > \n > Unpaginated? You must be kidding.\n > \n > (But if you are _that_ fast a reader, then hey, use \"PAGER=cat\", and \n > you'll find yourself happy).\n\nI used to do 'bk changes | grep \\[AGPGART\\] -C3 | head'  on a regular basis,\njust to be able to answer 'hey, did cset x get into tree y?' questions from users.\nwhich is the probably the closest I came to non-paginated usage.\n(though, ok 'head' is technically a pager too..)\n\n\t\tDave\n\n"},{"id":"1098","messageId":"2238.10.10.10.24.1114057679.squirrel@linux1","threadId":"177","inReplyTo":"20050420221451.36c98f62.rddunlap@osdl.org","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Sean","fromEmail":"seanlkml@sympatico.ca","sentAt":"2005-04-21T04:27:59Z","receivedAt":"2005-04-21T04:27:59Z","isPatch":false,"sender":{"key":"seanlkml@sympatico.ca","avatar":"https://gravatar.com/avatar/f92923f54fc08c401fc59b71829d4b89e9b8087fbba45ff87c82e6a83aee02ae?d=mp&s=160"},"body":"On Thu, April 21, 2005 1:14 am, Randy.Dunlap said:\n\n>> In _any_ real system you'll be getting thousands of lines of output.\n>> Possibly millions. unpaginated? What the hell are you talking about?\n>\n> Who in the world would look at thousands or millions of lines on a\n> tty using a pager?\n>\n\nThis conversation is getting a bit silly, but to answer your question a\npager has a search feature which would let you bypass the first 900,000\nlines to find the ones you're interested in.\n\nCheers,\nSean\n\n\n"},{"id":"1091","messageId":"20050421042833.GA10934@nevyn.them.org","threadId":"177","inReplyTo":"Pine.LNX.4.58.0504202056310.2344@ppc970.osdl.org","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Daniel Jacobowitz","fromEmail":"dan@debian.org","sentAt":"2005-04-21T04:28:34Z","receivedAt":"2005-04-21T04:28:34Z","isPatch":false,"sender":{"key":"dan@debian.org","avatar":null},"body":"On Wed, Apr 20, 2005 at 09:00:44PM -0700, Linus Torvalds wrote:\n> \n> \n> On Wed, 20 Apr 2005, Daniel Jacobowitz wrote:\n> > \n> > My logic: it's a lot more intuitive to say \"cg-log | less\" to get\n> > paginated output than it is to say \"cg-log | cat\" to get unpaginated\n> > output.\n> \n> I disagree.\n> \n> There is _never_ any valid situation where you do \"cg-log\" with \n> unpaginated output to a tty.\n> \n> In _any_ real system you'll be getting thousands of lines of output. \n> Possibly millions. unpaginated? What the hell are you talking about?\n\nOK, so I'm crazy.  I must have hallucinated doing this sort of thing on\na regular basis... :-) Examples: terminals with good scrollback,\nscreen, script.  Small repositories.  Irritation at less's habit of\nusing the alternate xterm buffer, whatever the technical term for that\nis.\n\nBut hey, you'll use it more often than I will by far.\n\n-- \nDaniel Jacobowitz\nCodeSourcery, LLC\n"},{"id":"1094","messageId":"7vll7cg1ir.fsf@assigned-by-dhcp.cox.net","threadId":"177","inReplyTo":"20050421042248.GA16002@redhat.com","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2005-04-21T05:08:28Z","receivedAt":"2005-04-21T05:08:28Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":">>>>> \"DJ\" == Dave Jones <davej@redhat.com> writes:\n\nDJ> I used to do 'bk changes | grep \\[AGPGART\\] -C3 | head' on a\nDJ> regular basis, just to be able to answer 'hey, did cset x\nDJ> get into tree y?' questions from users.  which is the\nDJ> probably the closest I came to non-paginated usage.\n\nI am bk untainted so I may be misunderstanding what your example\nis, but I take that \"bk changes\" in your example corresponds to\n\"git log\", correct?\n\nThen please read what Linus wrote again.  Your example is\nexactly the point Linus is making.  The output from that command\nis not going to a tty---it is going to a _pipe_ and more or less\nwill do exactly (not more or less ;-) the right thing.\n\n"},{"id":"1095","messageId":"20050420221451.36c98f62.rddunlap@osdl.org","threadId":"177","inReplyTo":"Pine.LNX.4.58.0504202056310.2344@ppc970.osdl.org","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Randy.Dunlap","fromEmail":"rddunlap@osdl.org","sentAt":"2005-04-21T05:14:51Z","receivedAt":"2005-04-21T05:14:51Z","isPatch":false,"sender":{"key":"rddunlap@osdl.org","avatar":null},"body":"On Wed, 20 Apr 2005 21:00:44 -0700 (PDT) Linus Torvalds wrote:\n\n| \n| \n| On Wed, 20 Apr 2005, Daniel Jacobowitz wrote:\n| > \n| > My logic: it's a lot more intuitive to say \"cg-log | less\" to get\n| > paginated output than it is to say \"cg-log | cat\" to get unpaginated\n| > output.\n| \n| I disagree.\n| \n| There is _never_ any valid situation where you do \"cg-log\" with \n| unpaginated output to a tty.\n| \n| In _any_ real system you'll be getting thousands of lines of output. \n| Possibly millions. unpaginated? What the hell are you talking about?\n\nWho in the world would look at thousands or millions of lines on a\ntty using a pager?\n\n| And as I pointed out, if the output is not a tty, then both less and more\n| automatically turn into cat, so there's no difference. This change _only_\n| triggers for a tty, and I dare you to show a single relevant project where \n| it's ok to scroll thousands of lines.\n| \n| Even git-pasky, which is just a two-week-old project right now outputs \n| 4338 lines of output to \"git log\". \n| \n| Unpaginated? You must be kidding.\n| \n| (But if you are _that_ fast a reader, then hey, use \"PAGER=cat\", and \n| you'll find yourself happy).\n\n---\n~Randy\n"},{"id":"1099","messageId":"20050421052930.GA27477@kroah.com","threadId":"177","inReplyTo":"Pine.LNX.4.58.0504201809170.2344@ppc970.osdl.org","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Greg KH","fromEmail":"greg@kroah.com","sentAt":"2005-04-21T05:29:30Z","receivedAt":"2005-04-21T05:29:30Z","isPatch":false,"sender":{"key":"greg@kroah.com","avatar":"https://gravatar.com/avatar/5bb5aa0cc2e01c00ec899d11130c07796bc186e465bae57bc34873b13b72c7c8?d=mp&s=160"},"body":"On Wed, Apr 20, 2005 at 06:12:34PM -0700, Linus Torvalds wrote:\n> \n> \n> On Wed, 20 Apr 2005, Linus Torvalds wrote:\n> > \n> > Pasky,\n> >  what do you think about this change to \"git log\"?\n> \n> Here's a slightly updated version.\n> \n> It's identical to the previous one, except that it also feeds the result \n> through \"| ${PAGER:-less}\" which makes it a lot more useful, in my \n> opinion.\n\nYeah!\n\nI've gotten tired of counting how many times I forgot to pipe 'git log'\nto less already.  Doesn't seem to want to be canceled either...\n\nthanks for doing this.\n\ngreg k-h\n"},{"id":"1101","messageId":"20050421064931.GA31910@pasky.ji.cz","threadId":"177","inReplyTo":"20050421042833.GA10934@nevyn.them.org","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Petr Baudis","fromEmail":"pasky@ucw.cz","sentAt":"2005-04-21T06:49:31Z","receivedAt":"2005-04-21T06:49:31Z","isPatch":false,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"Dear diary, on Thu, Apr 21, 2005 at 06:28:34AM CEST, I got a letter\nwhere Daniel Jacobowitz <dan@debian.org> told me that...\n> On Wed, Apr 20, 2005 at 09:00:44PM -0700, Linus Torvalds wrote:\n> > \n> > \n> > On Wed, 20 Apr 2005, Daniel Jacobowitz wrote:\n> > > \n> > > My logic: it's a lot more intuitive to say \"cg-log | less\" to get\n> > > paginated output than it is to say \"cg-log | cat\" to get unpaginated\n> > > output.\n> > \n> > I disagree.\n> > \n> > There is _never_ any valid situation where you do \"cg-log\" with \n> > unpaginated output to a tty.\n> > \n> > In _any_ real system you'll be getting thousands of lines of output. \n> > Possibly millions. unpaginated? What the hell are you talking about?\n> \n> OK, so I'm crazy.  I must have hallucinated doing this sort of thing on\n> a regular basis... :-) Examples: terminals with good scrollback,\n> screen, script.  Small repositories.  Irritation at less's habit of\n> using the alternate xterm buffer, whatever the technical term for that\n> is.\n\n... Plan9. But I guess you won't even have a pager there. ;-)\n\nA little off-topic, anyone knows how to turn off that damn alternate\nscreen thing on the xterm level? (Or any other level which makes _all_\nprograms not to use it.)\n\nMore seriously, I think Linus' patch is fine; the usage in scripts is\nnot affected, and alternatives were suggested. When we have cg-admin, I\nmight even let you set per-repository git-specific PAGER (which you\ncould set to be even some fancy script which would parse the stuff, open\na cute window and display stuff graphically, or whatever).\n\nLinus, ahem, could you please sign off your patch? :-)\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\nC++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor\n"},{"id":"1106","messageId":"20050421073601.GE31910@pasky.ji.cz","threadId":"177","inReplyTo":"u6hjj2-jl9.ln1@bd-home-comp.no-ip.org","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Petr Baudis","fromEmail":"pasky@ucw.cz","sentAt":"2005-04-21T07:36:01Z","receivedAt":"2005-04-21T07:36:01Z","isPatch":false,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"Dear diary, on Thu, Apr 21, 2005 at 04:53:33AM CEST, I got a letter\nwhere Bryan Donlan <bdonlan@bd.beginyourfear.com> told me that...\n> Fast-forwarding 55f9d5042603fff4ddfaf4e5f004d2995286d6d3 ->\n> 7a4c67965de68ae7bc7aa1fde33f8eb9d8114697\n> \ton top of 55f9d5042603fff4ddfaf4e5f004d2995286d6d3...\n> patch: **** Only garbage was found in the patch input.\n> \n> I'm on debian testing, patch 2.5.9. It seems to apply the changes\n> despite this error.\n\nHarmless, and fixed in latest.\n\nThanks for the report,\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\nC++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor\n"},{"id":"1108","messageId":"20050421074908.GA1376@elte.hu","threadId":"177","inReplyTo":"Pine.LNX.4.58.0504201503050.6467@ppc970.osdl.org","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Ingo Molnar","fromEmail":"mingo@elte.hu","sentAt":"2005-04-21T07:49:08Z","receivedAt":"2005-04-21T07:49:08Z","isPatch":false,"sender":{"key":"mingo@elte.hu","avatar":null},"body":"\n* Linus Torvalds <torvalds@osdl.org> wrote:\n\n> Yeah, yeah, it looks different from \"cvs update\", but dammit, wouldn't \n> it be cool to just write \"cg-<tab><tab>\" and see the command choices?  \n> Or \"cg-up<tab>\" and get cg-update done for you..\n\nadd this line to your ~/.bashrc:\n\n complete -W \"add addremote apply cancel ci commit diff export fork help init log ls lsobj lsremote merge pull rm seek status tag track version\" git\n\nand you'll get all the argument completions, after \"git \" (it works on \narguments, after the space). (you can even customize it to list only the \nones you typically use, to make the completion faster) This first showed \nup in zsh but now bash knows it too. (see 'Programmable Completions' in \nman bash)\n\n\tIngo\n"},{"id":"1131","messageId":"20050421162100.068146b9.froese@gmx.de","threadId":"177","inReplyTo":"20050421064931.GA31910@pasky.ji.cz","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Edgar Toernig","fromEmail":"froese@gmx.de","sentAt":"2005-04-21T14:21:00Z","receivedAt":"2005-04-21T14:21:00Z","isPatch":false,"sender":{"key":"froese@gmx.de","avatar":null},"body":"Petr Baudis wrote:\n>\n> A little off-topic, anyone knows how to turn off that damn alternate\n> screen thing on the xterm level? (Or any other level which makes _all_\n> programs not to use it.)\n\nChange the terminfo entry.\n\nThe relevant sequence is \\E?47h and \\E[?47l (save/restore screen) and\noften it is paired with \\E7 and \\E8 (save/restore cursor position)\nand \\E[2J (clear screen).  [1]\n\nHere it was put in the smcup/rmcup capabilities.\n\n  infocmp >term.src\n  vi term.src\n  # either remove the sequences or completely disable the\n  # capabilities by adding a dot in front of them (.rmcup=...).\n  tic term.src\n\nDone.\n\nCiao, ET.\n\n[1] On strange terminals the escape sequences may be completely\ndifferent but these are the common ones.\n"},{"id":"1145","messageId":"20050421164247.GJ30991@pasky.ji.cz","threadId":"177","inReplyTo":"20050421162100.068146b9.froese@gmx.de","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Petr Baudis","fromEmail":"pasky@ucw.cz","sentAt":"2005-04-21T16:42:47Z","receivedAt":"2005-04-21T16:42:47Z","isPatch":false,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"Dear diary, on Thu, Apr 21, 2005 at 04:21:00PM CEST, I got a letter\nwhere Edgar Toernig <froese@gmx.de> told me that...\n> Petr Baudis wrote:\n> >\n> > A little off-topic, anyone knows how to turn off that damn alternate\n> > screen thing on the xterm level? (Or any other level which makes _all_\n> > programs not to use it.)\n> \n> Change the terminfo entry.\n\nThat's why I asked for how to do it on the xterm level. Some programs\ndon't care about term(cap|info). And I may not be root.\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\nC++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor\n"},{"id":"1154","messageId":"4267EDD7.1070103@dwheeler.com","threadId":"177","inReplyTo":"pan.2005.04.21.02.48.19.802122@smurf.noris.de","subject":"Removing command dispatcher (was Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes)","fromName":"David A. Wheeler","fromEmail":"dwheeler@dwheeler.com","sentAt":"2005-04-21T18:15:51Z","receivedAt":"2005-04-21T18:15:51Z","isPatch":false,"sender":{"key":"dwheeler@dwheeler.com","avatar":"https://avatars.githubusercontent.com/u/813150?v=4"},"body":"Matthias Urlichs wrote:\n\n>Linus Torvalds wrote:\n>\n>  \n>\n>>I realize that there is probably a law that there has to be a space, but I \n>>actually personally use tab-completion all the time\n>>    \n>>\nIt's very unusual, but I can't think of any crisis it causes.\n\nOne minor annoyance: Windows doesn't support #! magic headers,\nand a very few-and-probably-ignorable old Unix systems don't either.\nThere, commands written in an interpreter like perl, python, or shell can't\nbe kicked off just by a #! reference at the top (standard Windows' shell is\nincompatible anyway, so it's just as well in the case of shell).\n\nI don't see this as a roadblock, though.  On those systems, you could\ncreate trivial stubs that just invoke the interpreter (e.g., perl) and the\nreal program. In the Windows case, you can use Windows' miserable\nexcuse for a command processor to do that very easily.\nE.g., if \"cg-update\" is a Perl script, then you can create a file \n\"cg-update.bat\":\nperl  \\path\\to\\cg-update %*\n\n(That requires Windows NT4 or better. MS-DOS didn't have %*, so you needed:\nperl  \\path\\to\\cg-update %1 %2 %3 %4 %5 %6 %7 %8 %9\nIt's hard to imagine an MS-DOS git user though.)\n\n--- David A. Wheeler\n\n"},{"id":"1443","messageId":"20050423170949.3fc879d9.pj@sgi.com","threadId":"177","inReplyTo":"20050421064931.GA31910@pasky.ji.cz","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Paul Jackson","fromEmail":"pj@sgi.com","sentAt":"2005-04-24T00:09:49Z","receivedAt":"2005-04-24T00:09:49Z","isPatch":false,"sender":{"key":"pj@sgi.com","avatar":null},"body":"> A little off-topic, anyone knows how to turn off that damn alternate\n> screen thing on the xterm level? \n\nDo you mean the 'feature' where it clears the screen of the\nlast page you were viewing on exit from 'less'?\n\nThe following stops that clearing:\n\n    export LESS=-X\n\n-- \n                  I won't rest till it's the best ...\n                  Programmer, Linux Scalability\n                  Paul Jackson <pj@engr.sgi.com> 1.650.933.1373, 1.925.600.0401\n"},{"id":"1444","messageId":"20050423171204.56c9d2d5.pj@sgi.com","threadId":"177","inReplyTo":"Pine.LNX.4.58.0504201809170.2344@ppc970.osdl.org","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Paul Jackson","fromEmail":"pj@sgi.com","sentAt":"2005-04-24T00:12:04Z","receivedAt":"2005-04-24T00:12:04Z","isPatch":false,"sender":{"key":"pj@sgi.com","avatar":null},"body":"Linus wrote:\n+\t\t\t\techo; sed 's/^/  /'\n\nOne can avoid adding useless trailing spaces on empty lines with:\n\n+\t\t\t\techo; sed 's/./  &/'\n\n-- \n                  I won't rest till it's the best ...\n                  Programmer, Linux Scalability\n                  Paul Jackson <pj@engr.sgi.com> 1.650.933.1373, 1.925.600.0401\n"},{"id":"1605","messageId":"20050425042722.5e06e5e8.akpm@osdl.org","threadId":"177","inReplyTo":"Pine.LNX.4.58.0504201503050.6467@ppc970.osdl.org","subject":"Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes","fromName":"Andrew Morton","fromEmail":"akpm@osdl.org","sentAt":"2005-04-25T11:27:22Z","receivedAt":"2005-04-25T11:27:22Z","isPatch":false,"sender":{"key":"akpm@osdl.org","avatar":null},"body":"Linus Torvalds <torvalds@osdl.org> wrote:\n>\n> Yeah, yeah, it looks different from \"cvs update\", but dammit, wouldn't it \n>  be cool to just write \"cg-<tab><tab>\" and see the command choices? Or \n>  \"cg-up<tab>\" and get cg-update done for you..\n\nzsh can do this for (for example) cvs.  Type \"cvs <tab><tab><tab>\" and \nyou get \"cvs annotate\".\n\nType \"cvs commit foo/bar/<tab>\" and zsh will start cycling through the \nfiles which need committing in ./foo/bar/.  Yes, the shell knows about\nand pokes around inside cvs files.\n\nI just brought this up because I know how much you'd love the whole\nconcept ;)\n"}]}