|
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
|
|
|
|
|
Nothing wrong with Models, Viewing and Controlling them 
|
|
|
|
|
John Simmons / outlaw programmer wrote: Docker containers... Why do they exist, and why should we care?
It solves the "it works on my machine" problem, which theoretically makes deployments easier and less error prone, especially when used with Kubernetes, which also takes care of dependencies and high availability.
Personally, I love .NET Core.
I like the way you can use the Startsup class in MVC Core and especially DI works nice.
.NET Core also gets updates a lot more often than .NET so my guess is that in a few years .NET Core will have more features than .NET.
I'm especially curious how .NET Core will become the language for Azure which will integrate will all services (currently .NET is still ahead on that).
And, of course, it's multi-platform, if that's what you need.
|
|
|
|
|
Way to go man!
|
|
|
|
|
Docker has made my life so much better. No sarcasm. 
"If we don't change direction, we'll end up where we're going"
|
|
|
|
|
I haven't yet learned what .Net core is for (my fault).
I can use .Net standard with WPF, Windows forms, Console, and UWP.
So I'm not motivated either.
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
|
|
|
|
|
maybe the .Net Microsoft team should give Marie Kondo a call ?
Marie Kondo: What is this?
MS: Its called .Net Core
Marie: Does it Spark Joy
MS: Absolutely not
Marie: Thank it, and then discard it
I'd rather be phishing!
|
|
|
|
|
Looks like a lot of change for change's sake: "I can't think of a genuine improvement, but I have to change something".
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
.net core is still 100% controlled and directed driven by ms:
some "open source" but it's absolutely not not "sharing with the community." it's "look [don't touch] at what we can do ...warranty void if this sticker is damaged."
... sharing is a 2 way process, with ms there is no sharing, zero, nada, it's showing.
it's "multi-platform:" sure, in the "lets make your platform do things our way or not at all."
and that is actually the largest risk factor of .net:
- no, not the "lets make your platform do things our way", it's the "our way" bit
yes, in any typical platform from any vendor an important risk factor is: what if they change or/and discontinue X". and regardless of vendor things will change, it can WILL happen with any platform vendor.
- most vendors will offer full explanations AS WELL AS workarounds, backward compatibility and even assistance with change.
- ms though [have many times demonstrated in the past] they will make change without explanation, with little or often no support and rarely if ever assistance, and will brook no feedback suggesting they have abandoned anyone.
@sanderrossel wrote: "I'm especially curious how .NET Core will become the language for Azure which will integrate will all services"
That actually makes me more worried that ms could as easily make .Net Core the only language for Azure which [only by itself] will integrate will all services (and vice-versa???)
and then there is the development tooling, [for sure away from windows, but sometimes even there too]: there's nothing that really covers all of the requirements for successfully managing all the factors of a large project without the need for quite frequent manual intervention. [Again true for many others too] and once more ms will rarely offer support or assistance.
(Let's face it, 98% of they way to 'fix' issues in any ms product has come from the on-line community: others suffering the same issues and banging away at poking sticks in it till they find something that works - because the no support from ms includes no provision of any decent technical documentation - hell even what does exist there nearly all came from the community.)
From a while back reading reviews, another [pro-ms] reviewer summed up .Net core thus (paraphrased):
"it's fine for a small/quick app to do one job, but really not a good choice for large and/or long term enterprise solutions."
Message Signature
(Click to edit ->)
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
