On 29.09.06, Marc Haber wrote: > Package: jed > Version: 0.99.18-5 > Severity: normal > > When using jed as the last element of a xargs pipe, such as > grep -l foo /some/path | xargs jed > to edit a lot of files containing some string, jed sometimes gets > confused. If one later decides to abort a jed command by typing > Ctrl-G, jed terminates silently and drops the user back to the shell. > Nothing is saved, and the terminal stays in a strange mode.
Also strange is, that a buffer *stdin* is opened alongside the listed files. ---- While we need upstream help and more testing to fix this, two workarounds are at hand: Either use jed `grep -l foo /some/path` or install the jed-extra package and use the grep() command from within jed. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
