{"thread":{"id":"9268","subject":"suggestion for git rebase -i","startedAt":"2007-07-28T04:58:20Z","lastAt":"2007-07-28T23:11:24Z","messageCount":7,"participants":["Seth Falcon","Johannes Schindelin","Jeff King"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"48866","messageId":"m26445t98z.fsf@ziti.fhcrc.org","threadId":"9268","inReplyTo":null,"subject":"suggestion for git rebase -i","fromName":"Seth Falcon","fromEmail":"sfalcon@fhcrc.org","sentAt":"2007-07-28T04:58:20Z","receivedAt":"2007-07-28T04:58:20Z","isPatch":false,"sender":{"key":"seth@userprimary.net","avatar":"https://gravatar.com/avatar/1db807504c1f8fb0a13bf1056a1e4d5096d17f3a09a1e9540f3af5f8b5ee009c?d=mp&s=160"},"body":"The tempfile used by git rebase -i is called \"todo\". For those using\nsomething like emacsclient, this is a bit too generic for the name of\na file in a pre-existing editor session. I realize this is a small\nnit, but how about renaming the file to \"git-rebase-todo\"?\n\n+ seth\n\n-- \nSeth Falcon | Computational Biology | Fred Hutchinson Cancer Research Center\nBioC: http://bioconductor.org/\nBlog: http://userprimary.net/user/\n"},{"id":"48879","messageId":"Pine.LNX.4.64.0707280941380.14781@racer.site","threadId":"9268","inReplyTo":"m26445t98z.fsf@ziti.fhcrc.org","subject":"Re: suggestion for git rebase -i","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-07-28T08:43:15Z","receivedAt":"2007-07-28T08:43:15Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Fri, 27 Jul 2007, Seth Falcon wrote:\n\n> The tempfile used by git rebase -i is called \"todo\". For those using\n> something like emacsclient, this is a bit too generic for the name of\n> a file in a pre-existing editor session. I realize this is a small\n> nit, but how about renaming the file to \"git-rebase-todo\"?\n\nWhy? This is an implementation detail, and should not concern the user.\n\nHowever, I was thinking about adding a \"git rebase --status\" to show where \nyou are, but that will have to be implemented by someone else, or it has \nto wait a little.\n\nCiao,\nDscho\n"},{"id":"48881","messageId":"20070728084550.GA13993@sigill.intra.peff.net","threadId":"9268","inReplyTo":"Pine.LNX.4.64.0707280941380.14781@racer.site","subject":"Re: suggestion for git rebase -i","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2007-07-28T08:45:51Z","receivedAt":"2007-07-28T08:45:51Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Sat, Jul 28, 2007 at 09:43:15AM +0100, Johannes Schindelin wrote:\n\n> > a file in a pre-existing editor session. I realize this is a small\n> > nit, but how about renaming the file to \"git-rebase-todo\"?\n> \n> Why? This is an implementation detail, and should not concern the user.\n\nBecause if you want to setup macros or syntax highlighting specific to\nediting git-rebase tempfiles, then you have to figure out somehow that\nyou are editing one. Using a more informative name for the tempfile\nmeans that you can guess based on the filename.\n\n-Peff\n"},{"id":"48886","messageId":"20070728085849.GB13993@sigill.intra.peff.net","threadId":"9268","inReplyTo":"20070728084550.GA13993@sigill.intra.peff.net","subject":"Re: suggestion for git rebase -i","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2007-07-28T08:58:49Z","receivedAt":"2007-07-28T08:58:49Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Sat, Jul 28, 2007 at 04:45:51AM -0400, Jeff King wrote:\n\n> > > a file in a pre-existing editor session. I realize this is a small\n> > > nit, but how about renaming the file to \"git-rebase-todo\"?\n> > \n> > Why? This is an implementation detail, and should not concern the user.\n> \n> Because if you want to setup macros or syntax highlighting specific to\n> editing git-rebase tempfiles, then you have to figure out somehow that\n> you are editing one. Using a more informative name for the tempfile\n> means that you can guess based on the filename.\n\nRe-reading his original message, I actually don't think this is what he\nwanted it for. But I think it's reasonable to give the tempfile a\nmeaningful name anyway for this reason.\n\n-Peff\n"},{"id":"48911","messageId":"m2vec4seyf.fsf@ziti.fhcrc.org","threadId":"9268","inReplyTo":"Pine.LNX.4.64.0707280941380.14781@racer.site","subject":"Re: suggestion for git rebase -i","fromName":"Seth Falcon","fromEmail":"sfalcon@fhcrc.org","sentAt":"2007-07-28T15:52:40Z","receivedAt":"2007-07-28T15:52:40Z","isPatch":false,"sender":{"key":"seth@userprimary.net","avatar":"https://gravatar.com/avatar/1db807504c1f8fb0a13bf1056a1e4d5096d17f3a09a1e9540f3af5f8b5ee009c?d=mp&s=160"},"body":"Johannes Schindelin writes:\n> Why? This is an implementation detail, and should not concern the\n> user.\n\nIn the context of an existing editing session, the name of the\ntempfile is visible and relevant to the user (not just an\nimplementation detail). For example, the tempfile name is useful when\nmulti-tasking and one needs to get back to the buffer. As another\nreply pointed out, the name could also be used for editor mode\ncustomization.\n\nSo. When editing a commit message, the buffer is named\nCOMMIT_EDITMSG. When editing a rebase -i buffer it is named todo. Is\nthis a real problem? Of course not. But I think a slightly more\ndescriptive name makes sense -- especially if other commands gain\ninteractive modes and a user might have a number of them going at once\n(in different repos, e.g.).\n\n+ seth\n"},{"id":"48929","messageId":"Pine.LNX.4.64.0707282109090.14781@racer.site","threadId":"9268","inReplyTo":"m2vec4seyf.fsf@ziti.fhcrc.org","subject":"Re: suggestion for git rebase -i","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-07-28T20:09:47Z","receivedAt":"2007-07-28T20:09:47Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Sat, 28 Jul 2007, Seth Falcon wrote:\n\n> Johannes Schindelin writes:\n> > Why? This is an implementation detail, and should not concern the\n> > user.\n> \n> In the context of an existing editing session, the name of the tempfile \n> is visible and relevant to the user (not just an implementation detail). \n> For example, the tempfile name is useful when multi-tasking and one \n> needs to get back to the buffer. As another reply pointed out, the name \n> could also be used for editor mode customization.\n\nOkay, fair enough. But since you want that feature, you get to do the \npatch. Hint: it is just one line that has to be changed.\n\nCiao,\nDscho\n"},{"id":"48939","messageId":"m2bqdwrun7.fsf@ziti.fhcrc.org","threadId":"9268","inReplyTo":"Pine.LNX.4.64.0707282109090.14781@racer.site","subject":"Re: suggestion for git rebase -i","fromName":"Seth Falcon","fromEmail":"sfalcon@fhcrc.org","sentAt":"2007-07-28T23:11:24Z","receivedAt":"2007-07-28T23:11:24Z","isPatch":false,"sender":{"key":"seth@userprimary.net","avatar":"https://gravatar.com/avatar/1db807504c1f8fb0a13bf1056a1e4d5096d17f3a09a1e9540f3af5f8b5ee009c?d=mp&s=160"},"body":"Johannes Schindelin writes:\n> Okay, fair enough. But since you want that feature, you get to do the \n> patch. Hint: it is just one line that has to be changed.\n\nHeh, I actually wrote the patch first, but thought it was so\ntrivial... :-)\n\nok, I will send the patch and hopefully not screw up the formatting,\netc. Feedback and hints welcome.\n\n+ seth\n"}]}