editor can't handle args in editor environment variables #32

Activity

1. fmoo commented on Jun 10, 2021

   

   fmoo

   on Jun 10, 2021

   Owner

   More actions

   Kind of an old issue. There's a PR for it (#15), but I wasn't sure if it would break editors with whitespace in their names.
2. carlcosmos commented on Jun 10, 2021

   

   carlcosmos

   on Jun 10, 2021 via email

   Author

   More actions

   Ah - I didn't catch that issue in advance. Feel free to dupe. Our workaround is to just parse the EDITOR variable before invoking editor. In particular we have a lot of users doing things like 'gvim -f' for a blocking gvim for their other uses cases. Would it suffice to look for things that look like an optparse/argparse style option? like the pattern " -<char>" or " --<chars>" (a space followed by dashes followed by chars) ? Thanks for responding,

   …

   -carl

   On Thu, Jun 10, 2021 at 1:10 AM Peter Ruibal ***@***.***> wrote: Kind of an old issue. There's a PR for it (#15 <#15>), but I wasn't sure if it would break editors with whitespace in their names. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#32 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUNNAKVTTSRPWFMKDO6RVSLTSBXPXANCNFSM46MSZ3RA> .