Bert Wesarg wrote: > Now I got your point. Maybe I should call GIT_EDITOR with $FILENAME as > argument but with a new variable to indicate open'n'forget. So > existing setups would always open the file (even without honoring the > line number) and new/smart wrappers can honor the open'n'forget and > line number flag. Yes, I like the communication-via-environment idea. In fact, there are multiple questions an editor might want answered: 1. GUI or no GUI? (The combination of $DISPLAY and $(tty) often yields a reasonable answer.) 2. open'n'forget or wait for answer? (gvim's --nofork option) 3. What line number? 4. regex to use to highlight matches? Ideally $LINENUMBER would only be used represent (3), while a separate variable would indicate (2). -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html