Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>Write a script</strong></p> <p>It would take some work, but you could write a script to front end as your SVN_EDITOR. When <code>svn</code> invokes your SVN_EDITOR, it passes the name of an svn-generated temporary comment file containing the summary list of affected files to be committed.</p> <p><a href="http://svnbook.red-bean.com/en/1.5/svn-book.html#svn.advanced.externaleditors" rel="nofollow">http://svnbook.red-bean.com/en/1.5/svn-book.html#svn.advanced.externaleditors</a></p> <blockquote> <p>The value of any of these options or variables is the beginning of a command line to be executed by the shell. Subversion appends to that command line a space and the pathname of a temporary file to be edited. So, to be used with Subversion, the configured or specified editor needs to support an invocation in which its last command-line parameter is a file to be edited, and it should be able to save the file in place and return a zero exit code to indicate success.</p> </blockquote> <p>Conceivably, you could write a shell script that takes a filename parameter that:</p> <ol> <li>opens the file indicated by the last arg (the svn temporary comment file)</li> <li>parses it for the files to be committed</li> <li>runs <code>svn diff</code> on each modified (non-binary) file and appends the diff output back to the end of the svn temporary comment file</li> <li>invokes your real editor on the modified svn temporary comment file</li> </ol> <p>Make sure your script returns the return code returned by your real editor or 0 to indicate success. Then set your SVN_EDITOR env var to point to your script.</p> <p>Perhaps someone has already written such a script, but I couldn't find one (especially since you didn't indicate an OS). There's also a good chance that this script could generate an extremely large file.</p> <p><strong>Alternative - write a macro</strong></p> <p>I think a better alternative would be to use a programmable editor and program a macro that read a filename(s) from some selected line(s) and then run SVN diff on the file(s) - putting the results in a buffer or appending it to current buffer . You could then selectively highlight files from the svn temporary comment file and run SVN diff on just the key files you need. Sounds like a job for elisp!</p> <p><em>Sorry I don't have an ready-made code for you. If you do either of these, it would be interesting to see come back and post your script/macro back here as an answer.</em></p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload