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

Re: Alternative to manual editing with git add --patch

From
Sven Helmberger <sven.helmberger@gmx.de>
Date
Oct 15, 2015, 13:37 UTC
Message-ID
<561FAC12.5020007@gmx.de>
In-Reply-To
<alpine.DEB.1.00.1510151152470.31610@s15462909.onlinehome-server.info>
Am 15.10.2015 um 12:11 schrieb Johannes Schindelin:
> 
> This is all technically sound. From a usability perspective I would wish
> more for a way to exclude or filter the lines by a pattern. 
Why not do both?
The only thing that is unfortunate is that the "/" already is a command.

Which would point to either a solution along the lines of "s<range>" being the split-by-line and "s/" being the split-by-regex?

Or is this an argument for introducing yet another interaction mode entered when "s" fails to split further -- with simple "/" and "<range>" being the options in that mode.

Regards, Sven Helmberger

Previous: Johannes SchindelinNext: Johannes Schindelin
Message 7 of 9 in “Alternative to manual editing with git add --patch”
  1. Sven HelmbergerOct 14, 2015
  2. Matthieu MoyOct 14, 2015
  3. Johannes SchindelinOct 14, 2015
  4. Junio C HamanoOct 14, 2015
  5. Sven HelmbergerOct 14, 2015
  6. Johannes SchindelinOct 15, 2015
  7. Sven HelmbergerOct 15, 2015
  8. Johannes SchindelinOct 15, 2015
  9. Sven HelmbergerOct 15, 2015

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.