> (exit (system*/exit-code "/usr/bin/vi" "filename"))
On a slightly unrelated note, if this for consumption by anyone other than
just you, I would use (getenv "EDITOR") (or VISUAL, if you prefer) rather
than hard-code the path to vi.
Best,
D. Ben Knoble
--
You received this message because
Ben, hello.
On 4 Aug 2021, at 16:45, D. Ben Knoble wrote:
On a slightly unrelated note, if this for consumption by anyone other
than
just you, I would use (getenv "EDITOR") (or VISUAL, if you prefer)
rather
than hard-code the path to vi.
An excellent point.
In fact this is indeed a
> started as a quick experiment with scsh a number of years ago,
Iām surprised no one has mentioned Rash so I will ... perhaps Rash will be a
useful tool for you ...
https://docs.racket-lang.org/rash/
ā2 Rash Guide ... Rash is a shell language embedded in Racket. ā
https://rash-lang.org/
Hi Norman,
> It's slightly unfortunate that Racket's
> start-up time make it slightly suboptimal as a command-line tool, but
> raco make helps with that.
With 8.0+/CS, even without make I've had a good experience. As you
say, setup or make makes things even faster, though.
If you weren't
Many thanks for your thoughts, George and Shu-Hung.
Rather embarassingly, I've found my answer in what's almost the simplest
subprocess procedure:
(exit (system*/exit-code "/usr/bin/vi" "filename"))
exhibits the behaviour I want. That does all the required plumbing
flawlessly.
I'm
5 matches
Mail list logo