|
Genuinely wondering how well IntelliSense would work at a command prompt.
We're all familiar with how it works in VS, VS Code and other environments that have implemented the idea. I'm trying to picture the same thing at a command prompt (cmd.exe or a PowerShell session)...would it help, or just get in the way? Although in an ideal world this would be a user setting.
The history buffer (up/down) and tab completion are already big time savers...so why haven't we seen an all-out version of IntelliSense with full context sensitivity for the command prompt yet...?
Would this get any upvote on a MS feedback page (or Windows Insider), or is this a waste of time?
|
|
|
|
|
Nothing wrong with the idea. You can do an incremental search and display in another window while a user is typing (like a "spell checker").
(I think the extra window makes it more impressive ... sort of AI like. But not like Clippy).
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
Gerry Schmitz wrote: sort of AI like. But not like Clippy
clippy was artificial?
Message Signature
(Click to edit ->)
|
|
|
|
|
Intellisense has the bad habit of always insisting on showing me only what I don't intend to use and carefully avoids showing that variable I just had declared only after I am as good as done typing its name. Sometimes of course it is unable to when I did not care to declare anything previously. It's just too dumb to follow my course of thinking, since I refuse to be trained to the One Microsoft Way (TM) of doing things by this silly gadget.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
I "had" to turn it off at one time; I felt as you did (different MS tool). Distracting.
Now it's the team member that you were told to find a place for.
And one can improve on what came before.
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
I imagine it could show you ghost letters of what the result of pressing tab could be, or maybe some kind of overlay similar to the IntelliSense menu that could could traverse with up/down keys. I never liked how you can wipe out what you're typing by pressing the up key anyway so that's functionality we can afford to lose.
What could be cooler is some NLU that could convert plain English (or whatever language) into commands - who needs autocomplete if you could just type
FOO=$(nlu-cmd "list of all markdown files that have been updated this year")
|
|
|
|
|
You can look at (in a VM, of course) some old text editors, WPs, and IDEs to get an idea how similar things were done before windowed apps became the norm. Some are quite easy to use and intuitive, so they might give you some good ideas. Have a browse through abandonware sites, to find them.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
dandy72 wrote: a waste of time?
It depends on how much you have...
The tab-competition feature came after more than a decade...
History still local (if you close the command window or restart the computer it start afresh)...
If you are looking for extend/improve something it is probably better to go with PowerShell...
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
|
|
|
|
|
PowerShell is what I had in mind as a model.
VS Code has some nice extensions that provide context-sensitive IntelliSense for PowerShell, probably because PowerShell has some pretty clear rules and established standards.
|
|
|
|
|
Ever used bash with autocompletion? It's a huge timesaver.
GCS d--(d+) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
Doesn't tab just cycle through available options? I'm thinking rather some sort of popup window like you get in the VS IDE.
|
|
|
|
|
Not in bash (well - you have options - many options!). WIth bash, if you press TAB twice, it lists the options you have, whether that's files, commands or command options. For example - if I type git c at the command line and then TAB twice, I get the following:
u404261@cabbage:/h/GR6-Detector$ git c
checkout cherry-pick clang-format-6.0 clean co config
cherry ci clang-format-7 clone commit
These are the available completions (and I wasn't aware of git-clang-format before, so I've learnt something there!). And going by this page, you can then bind keys to select from that list...
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
Definitely! And it's even more than just that double tab idea: https://www.thegeekstuff.com/2013/12/bash-completion-complete/
Though I think tying onto the manpage as an NCurses "pop-up-window" may even be surpassing this. Unfortunately I don't know how to get that working. Would likely need to have some specialized terminal client.
Haven't used this before, but from the feature set it seems to come close: fish shell
|
|
|
|
|
dandy72 wrote: with full context sensitivity for the command prompt yet...
Because it would be a huge overengineering ?
Not sure what is your job, but for the few times I have to use the command prompt, completion tab was fully sufficient.
|
|
|
|
|
Rage wrote: Because it would be a huge overengineering ?
As per one of my responses above, VS Code has some PowerShell extensions that can do a very nice job of it because PowerShell has some pretty standard methods for exposing methods, params, help and such.
If we could get those for Powershell sessions, rather than just editors, I think it'd be a great start.
|
|
|
|
|
You already have that, in the PowerShell IDE. Would it help to have it while using PS or CMD? Well, maybe. I'd give it an upvote.
I only have a signature in order to let @DalekDave follow my posts.
|
|
|
|
|
That's exactly what I had in mind. If the IDE can do it, then it sure would be nice (I have to think) to also have that right at an interactive command prompt.
|
|
|
|
|
Spent some time with the PowerShell ISE yesterday which has IntelliSense and hell yes, it helped a huge lot. From that perspective, it being great on the console itself is a no-brainer, roll it!
|
|
|
|
|
Already available (in a text UI) with bash, and probably with zsh or fish as well.
Full context sensitivity really requires help from the programs you use, if it's going to provide useful suggestions for things like program options. For example, if I type git c at a command line, I get a list of git commands starting with 'c'. I've just looked in the various bash autocompletion areas on my WSL install, and there's close to 1000 completion scripts for different programs' options, all installed when I apt install a package.
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
Research the HP/DEC/Digital Vax VMS VERB architecture.
A structured command line definition like that would be easy to provide intellisense for versus scads of external .exe files.
It made it easy to add and remove commands(VERBS) from a user's login assigned cmd shell.
|
|
|
|
|
I use a command prompt A LOT...
Auto complete (TAB) is wonderful.
a CTRL-TAB feature that shoves the COMMAND REFERENCE in the status bar, or opens a new command window with [COMMAND] /HELP, just to remind me the parameters/options, would be an 80/20 solution that I would think was almost trivial to implement!
For windows, I used AutoHotKey and created Win-G which (although G is for Google, I use DuckDuckGo), it takes the selected text and does a search on it in a browser page. I use it 90% of the time for spell checking in unfriendly programs, and sometimes to do a quick lookup... (It does not work on a CMD prompt, but it is not my target, either)...
|
|
|
|
|
Does anyone else feel like the introduction of .Net core is introducing needless contention, obfuscation, clutter, and/or ambiguity of the overall .Net landscape?
It feels like .Net Core is in the same category as Docker containers... Why do they exist, and why should we care?
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
|
It's the work of the devil, my naive colleagues took the bait and now expect me to clean up the mess that it causes on the builder 
|
|
|
|
|
So, have you suggested starting over with MVC5 yet? 
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
