Ric wrote >Am I right in saying that essentially you are creating an empty prompt in the history that you can go back to?
Yes, that's right. >I can see this could be useful when working in the Terminal. However I'm not sure it will help with the issue I'm trying to solve. Now you've explained it better than I could glean from the thread, I'm apt to agree. It so happened I was tussling with a similar problem in an experimental IDE I'm playing with. But I've not been a Windows user for 20 years and don't feel qualified to add anything useful to what I wrote. So I'll just quietly bow out. Ian On Mon, 26 Apr 2021 at 22:11, Ric Sherlock <[email protected]> wrote: > Hi Ian, > Am I right in saying that essentially you are creating an empty prompt in > the history that you can go back to? > > I can see this could be useful when working in the Terminal. However I'm > not sure it will help with the issue I'm trying to solve. > > The scenario: > A J terminal session is open. There is an unexecuted sentence on the > command line. The cursor is positioned in the middle of the sentence. > A script editor session is open and currently has focus. > The user uses a keyboard shortcut (Ctrl+r) to send the current line in the > editor to the terminal to be executed. > > The result: > In a JQt session the unexecuted sentence on the command line is expunged, > the line from the editor is copied to the terminal and the line is > executed. > In a VSCode session that uses Linux jconsole terminal, this is now also the > behaviour. > In a VSCode session that uses Windows jconsole.exe terminal, the command > line is not expunged and the line from the editor is copied to the terminal > command line at the position of the cursor, then the line is executed > (likely with unpredictable behaviour depending on the sentence!) > > I'm not sure how I could reliably access the empty prompt from the command > line history? > > Thanks > > > > On Mon, Apr 26, 2021 at 9:16 PM Ian Clark <[email protected]> wrote: > > > Pardon my crazy solution, but it works for me (with jconsole on > Terminal), > > and is worth doing if you find yourself needing to clear the command > line a > > lot. It might just work on non-Mac platforms too. > > > > Enter a single space. > > (Just pressing Enter won't work) > > This empty line can now be recovered like any past input via the arrow > > keys. > > > > Oddly, the space doesn't reappear, and it looks like a clean prompt. > > > > On Mon, 26 Apr 2021 at 04:00, Ric Sherlock <[email protected]> wrote: > > > > > Thanks Greg, > > > I've just released a new version (0.7.4) that doesn't attempt to clear > > the > > > current terminal command line if it detects jconsole.exe. > > > If there was a way to clear the cmdline for jconsole.exe it could be > > added, > > > in the meantime the remote WSL experience is much more predictable! > > > > > > Thanks, > > > > > > On Mon, Apr 26, 2021 at 2:13 PM greg heil <[email protected]> wrote: > > > > > > > Ric > > > > > > > > Forewarned is forearmed:) > > > > even a "feature"!-) > > > > > > > > Either ctrl-e or ctrl-r > > > > plunk the code > > > > at the terminals cursor > > > > before execution > > > > > > > > ctrl-r plunks the whole line > > > > including leading/trailing blanks > > > > no line-feeds etc > > > > > > > > BTW thanks for the contribution! > > > > > > > > ~greg > > > > https//picsrp.github.io > > > > > > > > -- > > > > > > > > from: greg heil <[email protected]> > > > > to: General forum <[email protected]> > > > > date: Apr 25, 2021, 6:13 PM > > > > subject: Re: [Jgeneral] How to clear the current line in the Windows > > > > Jconsole? > > > > > > > > Ric > > > > > > > > Ah feel less timid:-) > > > > i would not say broken > > > > both 072 and 073 > > > > have the same "mixed" affect > > > > on my WX > > > > > > > > ~greg > > > > https//picsrp.github.io > > > > > > > > -- > > > > > > > > from: Ric Sherlock <[email protected]> > > > > reply-to: [email protected] > > > > to: General forum <[email protected]> > > > > date: Apr 25, 2021, 4:46 PM > > > > subject: Re: [Jgeneral] How to clear the current line in the Windows > > > > Jconsole? > > > > > > > > Hi Greg, > > > > > > > > >Yes it updates via the VSCode extensions interface. Note that it is > > > > pretty easy to use an older version. Just go to the J entry in the > > > > Extensions sidebar, click on the Cog, click "Install another > > Version...", > > > > and choose the version you want to install. > > > > > > > > >I've pretty much standardised on using WSL for my development - > which > > is > > > > why I didn't realise until later that I'd broken the "send to > terminal" > > > > hotkey experience for native Windows J. I'm actually looking forward > to > > > > WSLg because I'm hoping I can get access to GUI facilities from J > > running > > > > in WSL. > > > > > > > > >My understanding is that WSLg is using Wayland (rather than X11) and > > > that > > > > rather than "imposing Win graphics" on remote Linux connections, it > > will > > > > let Linux use the Windows GPU to present Linux graphics on Windows. > > > > > ---------------------------------------------------------------------- > > > > For information about J forums see > http://www.jsoftware.com/forums.htm > > > > > > > ---------------------------------------------------------------------- > > > For information about J forums see http://www.jsoftware.com/forums.htm > > > > > ---------------------------------------------------------------------- > > For information about J forums see http://www.jsoftware.com/forums.htm > > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
