Re: [j-nsp] Junos 21+ Killing Finger Muscle Memory - Resolved

And thank you all that responded to the request to open cases. Easy contributions to make the case, and far fewer meetings to resolve than it could have been. -- Jeff (who made noise, but did no source code commits) On 10/19/23, 12:48 AM, "juniper-nsp on behalf of Chris Kawchuk via

Re: [j-nsp] Junos 21+ Killing Finger Muscle Memory - Resolved

On 10/19/23 06:48, Chris Kawchuk wrote: Indeed. Apologies to all --- I too got an update from JNPR on the "show route" vs "show routing" CLI conflict a few weeks ago in early September -- but forgot to share it here. CASE; 2023-0719-733950 Synopsis: "show route" and "show routing"

Re: [j-nsp] Junos 21+ Killing Finger Muscle Memory - Resolved

Indeed. Apologies to all --- I too got an update from JNPR on the "show route" vs "show routing" CLI conflict a few weeks ago in early September -- but forgot to share it here. CASE; 2023-0719-733950 Synopsis: "show route" and "show routing" operational mode CLI conflict - JunOS 21+ Root

Re: [j-nsp] Junos 21+ Killing Finger Muscle Memory...

for good news to pass along in the near future. -- Jeff Juniper Business Use Only From: Chris Lee Date: Wednesday, July 26, 2023 at 10:16 PM To: Jeff Haas , "juniper-nsp@puck.nether.net" Subject: Re: [j-nsp] Junos 21+ Killing Finger Muscle Memory... [External Email. Be cautious

Re: [j-nsp] Junos 21+ Killing Finger Muscle Memory...

On July 26, 2023 7:15:55 PM PDT, Chris Lee via juniper-nsp wrote: >Hi Jeff, > >Any chance the CLI could make use of repeated presses of the TAB key to >cycle through the completion options ? > >For instance in the newer 21.x release for EX switches I note a >"synchronous-ethernet" option under

Re: [j-nsp] Junos 21+ Killing Finger Muscle Memory...

On 7/19/23 06:22, Mark Tinka wrote: I'm trying with my SE too. Let's stay in touch. Got a ticket opened with JTAC which my SE upstreamed, and it has been linked to an internal PR that was raised on the back of Chris' ticket. So all we can do now is wait. Thanks, all. Mark.

Re: [j-nsp] Junos 21+ Killing Finger Muscle Memory...

Hi Jeff, Any chance the CLI could make use of repeated presses of the TAB key to cycle through the completion options ? For instance in the newer 21.x release for EX switches I note a "synchronous-ethernet" option under the show level, and my muscle memory for "show system" was reduced down to

Re: [j-nsp] Junos 21+ Killing Finger Muscle Memory...

On 7/19/23 02:37, Chris Kawchuk wrote: Hi Jeff I'll open it with my SE here in Australia (Mark Barrett). Will advise once complete. I'm trying with my SE too. Let's stay in touch. Mark. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net

Re: [j-nsp] Junos 21+ Killing Finger Muscle Memory...

Hi Jeff I'll open it with my SE here in Australia (Mark Barrett). Will advise once complete. - CK. > On Jul 19, 2023, at 01:24, Jeff Haas via juniper-nsp > wrote: > > > Juniper Business Use Only > On 7/12/23, 12:11 PM, "Jeff Haas" > wrote: >> On 7/12/23, 11:46

Re: [j-nsp] Junos 21+ Killing Finger Muscle Memory...

Juniper Business Use Only On 7/12/23, 12:11 PM, "Jeff Haas" mailto:jh...@juniper.net>> wrote: > On 7/12/23, 11:46 AM, "Mark Tinka" mailto:m...@tinka.afri> > >ca> wrote: > > Will any of these issues register significantly on Juniper's roadmap of >

Re: [j-nsp] Junos 21+ Killing Finger Muscle Memory...

On Sun, 16 Jul 2023 at 19:47, Tim Franklin via juniper-nsp wrote: > You missed the fun part where you have to explain *again* every few > months to the CISO and their minions why you can't adhere to the > written-by/for-Windows-admins "Patching Policy" that says everything in > the company is

Re: [j-nsp] Junos 21+ Killing Finger Muscle Memory...

On 16/07/2023 00:51, C K via juniper-nsp wrote: Indeed. And as you’re alluding to and most probably already know this — yeah most of us end up settling on “some release train” for a while, after we spend 3-4 months testing it thoroughly in the Lab... then spend 18 months getting everything

Re: [j-nsp] Junos 21+ Killing Finger Muscle Memory...

Indeed. And as you’re alluding to and most probably already know this — yeah most of us end up settling on “some release train” for a while, after we spend 3-4 months testing it thoroughly in the Lab... then spend 18 months getting everything in the network “up to that release”. With hundreds

Re: [j-nsp] Junos 21+ Killing Finger Muscle Memory...

On 7/15/23 20:54, Crist Clark wrote: I find it kind of telling that customers are just getting around to complaining about it two years after it was released. Not at all surprising, but illustrates how slow network operators update cycles can be compared to the pace of development. To

Re: [j-nsp] Junos 21+ Killing Finger Muscle Memory...

I find it kind of telling that customers are just getting around to complaining about it two years after it was released. Not at all surprising, but illustrates how slow network operators update cycles can be compared to the pace of development. To the Junos developers, this is ancient news, long

Re: [j-nsp] Junos 21+ Killing Finger Muscle Memory...

Hi Mark, 100% agree if it could help. Very annoying. If UX designer touched it, he or she probably never actually worked with Junos. Kind regards, Andrey Mark Tinka via juniper-nsp писал(а) 2023-07-12 04:49: So, this is going to be a very priviledged post, and I have been spending the last

Re: [j-nsp] Junos 21+ Killing Finger Muscle Memory...

On 7/12/23, 11:46 AM, "Mark Tinka" mailto:m...@tinka.afri>ca> wrote: > Will any of these issues register significantly on Juniper's roadmap of > how to make customers happier? Likely unlikely. Cynically, money moves things the best. But these comments don't fall on deaf ears. Occasionally,

Re: [j-nsp] Junos 21+ Killing Finger Muscle Memory...

On 7/12/23 15:45, Jeff Haas wrote: You don't need to tell my fingers that. __ With the infrastructure as it is, the only "solution" is we stop adding things. Good luck with that. The general here is the explosion of keywords. I have about 15 features sitting in my backlog that are

Re: [j-nsp] Junos 21+ Killing Finger Muscle Memory...

On 7/12/23 15:38, Chris Wopat wrote: Another offender in 21. `protocols bgp` doesn't autocomplete as it did since `bgpmcast` was added. me@r-mx304-lab-re1# set protocols bgp? Possible completions: > bgp                  BGP options > bgpmcast             BGP multicast options Yes, that

Re: [j-nsp] Junos 21+ Killing Finger Muscle Memory...

On 7/12/23 15:08, Vladimir Blazhkun wrote: You can probably deny that command using the login class ACL. As I'd mentioned to someone else already, not looking to create custom hacks that would not survive staff movement. While it is an option, it would be one of extreme last resort.

Re: [j-nsp] Junos 21+ Killing Finger Muscle Memory...

You don't need to tell my fingers that. __ With the infrastructure as it is, the only "solution" is we stop adding things. Good luck with that. The general here is the explosion of keywords. I have about 15 features sitting in my backlog that are small things to do to bgp policy. The policy

Re: [j-nsp] Junos 21+ Killing Finger Muscle Memory...

Another offender in 21. `protocols bgp` doesn't autocomplete as it did since `bgpmcast` was added. me@r-mx304-lab-re1# set protocols bgp? Possible completions: > bgp BGP options > bgpmcast BGP multicast options

Re: [j-nsp] Junos 21+ Killing Finger Muscle Memory...

You can probably deny that command using the login class ACL. -- Vladimir Blazhkun (via iPhone). > On 12 Jul 2023, at 11:49, Mark Tinka via juniper-nsp > wrote: > > So, this is going to be a very priviledged post, and I have been spending > the last several months mulling over even

Re: [j-nsp] Junos 21+ Killing Finger Muscle Memory...

On 7/12/23 11:12, Chris Kawchuk wrote: +1 Mark! For transparency, it was Chris who gave me the nudge, so thanks for that, mate :-). As any good problem begs for a solution, my suggestions to JNPR are as follows, as alternative places for this command: "show route transport-class

Re: [j-nsp] Junos 21+ Killing Finger Muscle Memory...

+1 Mark! As any good problem begs for a solution, my suggestions to JNPR are as follows, as alternative places for this command: "show route transport-class ..." (or really, is it even a routing thing? might be better w/the segment-routing or spring commands)i.e.: "show segment-routing ..."

[j-nsp] Junos 21+ Killing Finger Muscle Memory...

So, this is going to be a very priviledged post, and I have been spending the last several months mulling over even complaining about it either on here, or with my SE. But a community friend sent me the exact same annoyance he is having with Junos 21 or later, which has given me a final