« first day (1177 days earlier)      last day (634 days later) » 

3:29 PM
Actually, the overhaul is already done on the dev branch, it's just missing arg input
 
@DJMcMayhem cool, I noted it in my github feed, looking forward to it
does/will it support watching the V code run "live"?
 
Unfortunately no, I'm not exactly sure how to do that
If you want to watch it live, probably the best way is to do vim -u vim/init.vim and manually type it out
(Assuming your terminal can interpret meta-keys)
@Cowsquack Actually, you sort of could if you open up a vim input -u vim/init.vim and then run :call Execute_Program("path/to/source", "verbose") where "verbose" is a 0 or 1 for whether you want verbose mode.
I'm a total bash noob, so I'm not exactly sure what the best way to escape a bash-string to pass to vimscript is. I'm thinking the most foolproof way would be just a list of ASCII codes, but if someone else knows a better way I'm all ears
@DJMcMayhem Although that might need an another arg to optionally sleep between each key so that it isn't too fast. Which means ñ/ò would need that too. Hmm...
 
@DJMcMayhem (looking at the GH issue) the issue about xterm was for debug mode, but there probably exists some program that does that for you
@DJMcMayhem in what context do you want to pass it to vimscript?
 
DJMcMayhem has unfrozen this room.
 
This room has been dead for over a year, jeez
11 messages moved from The Nineteenth Byte
@Cowsquack So I want to take each extra arg (in bash I suppose that's $2 and up) and do something like -c 'call setreg("a", "$2")' -c 'call setreg("b", "$3")' etc.
 
3:41 PM
brb in a while
 
@Cowsquack Oh and speaking of the arg inputs, there's a new useful feature. Ñ now evaluates to the number of args, so you could do something like ÑñÀé*o<esc>
2
A: Invert Some Switches on a Switchboard

DJMcMayhemV, 20 bytes ÑñÀ/vüÞ sv^l?Ö" xH Try it online! Uses some new features, such as Ñ which is incredibly useful.

For a practical example
 
4:32 PM
@DJMcMayhem something like this? tio.run/…
 
Yeah, but I need it to work for arbitrary strings without breaking vim
 
ah, I see the problem now
 
So I was thinking that I would just do a list of ASCII values
 
unix.stackexchange.com/a/92448/216467 shows how to get the ascii value for a character
 
Yeah, I think I know how I could do it, I'm just wondering if there's a neater way
There's also stackoverflow.com/a/27817504/3524982, but that's for bash, so I don't know if it would work for vimscript also
 
4:50 PM
doesn't appear to because of the $'' strings
maybe ask on tnb
 
Actually, the other thing I could do that would be easier than a list of ASCII values is a string like "\xXX\xXX..." since then vim doesn't have to do any more work
That'll probably be the best way
 
5:08 PM
then do you have a way to convert it to that format in bash?
 
Probably just printf in a loop
 
 
6 hours later…
10:50 PM
I think the rework is done now
 

« first day (1177 days earlier)      last day (634 days later) »