Sat, 09 Dec 2017 12:33:30 -0700 "Theo de Raadt"
> > Sat, 09 Dec 2017 12:02:07 -0700 "Theo de Raadt"
> > > > With all the respect and understanding what you're saying is true, yet
> > > > I have the time to change my prompt, and it would still affect me.
> > >
> > > If you have changed it,
> But we should probably keep the POSIX default for sh. POSIX doesn't
> cover csh, so we're free to do what we want here too.
>
> So my proposal is to make the change, but stick with the current
> default for ksh-invoked-as-sh.
Seriously, can anyone find one reason other than "dusty papers"?
> From: "Theo de Raadt"
> Date: Sat, 09 Dec 2017 11:38:44 -0700
>
> > this just feels like a needless deviation.
>
> all i can say is:
>
> bash-4.4$
Which is perfectly fine for bash since it isn't the POSIX shell when
invoked as bash. For the same reason we can do what we want for ksh.
But w
On 12/9/2017 1:28 PM, Bryan Steele wrote:
> On Sat, Dec 09, 2017 at 06:44:44PM +0100, Theo Buehler wrote:
>> This was discussed in a smaller circle and has been in snaps for two
>> days, but I'd like to show this to a wider audience.
>>
>> Theo asked me to make sure that all our shells print a pr
On Sat, December 9, 2017 3:44 pm, Theo Buehler wrote:
> This was discussed in a smaller circle and has been in snaps for two
> days, but I'd like to show this to a wider audience.
>
> Theo asked me to make sure that all our shells print a prompt including
> the hostname by default. The reasoning is
> Sat, 09 Dec 2017 12:02:07 -0700 "Theo de Raadt"
> > > With all the respect and understanding what you're saying is true, yet
> > > I have the time to change my prompt, and it would still affect me.
> >
> > If you have changed it, it is irrelevant what the value was before
> > the change. You
On 2017-12-09 1:10 PM, Theo de Raadt wrote:
the default prompt works exactly because it doesn;t try to second guess
what the user wants, or what is or isn;t good for them. the mechanism
for changing the prompt is trivial.
i don;t think it makes sense to change the shells in this way.
Having see
On Sat, Dec 09, 2017 at 06:44:44PM +0100, Theo Buehler wrote:
> Theo asked me to make sure that all our shells print a prompt
> including the hostname by default.
Thank you. This is a significant improvement.
I keep finding myself updating /etc/profile everywhere to ensure I don't
lose my bearing
Sat, 09 Dec 2017 12:02:07 -0700 "Theo de Raadt"
> > With all the respect and understanding what you're saying is true, yet
> > I have the time to change my prompt, and it would still affect me.
>
> If you have changed it, it is irrelevant what the value was before
> the change. You detail no i
As a server admin, I adore the idea. I've yelled profanity too many times
rebooting the wrong machine in haste. Would be wonderful in a large tmux
session.
On Dec 9, 2017 11:57, wrote:
Sat, 09 Dec 2017 11:10:03 -0700 "Theo de Raadt"
> > the default prompt works exactly because it doesn;t try to
> With all the respect and understanding what you're saying is true, yet
> I have the time to change my prompt, and it would still affect me.
If you have changed it, it is irrelevant what the value was before
the change. You detail no impact. You appeal is 100% emotion.
Sat, 09 Dec 2017 11:10:03 -0700 "Theo de Raadt"
> > the default prompt works exactly because it doesn;t try to second guess
> > what the user wants, or what is or isn;t good for them. the mechanism
> > for changing the prompt is trivial.
> >
> > i don;t think it makes sense to change the shells i
On Sat, Dec 09, 2017 at 06:33:32PM +, Jason McIntyre wrote:
> On Sat, Dec 09, 2017 at 11:10:03AM -0700, Theo de Raadt wrote:
> > > the default prompt works exactly because it doesn;t try to second guess
> > > what the user wants, or what is or isn;t good for them. the mechanism
> > > for changi
> this just feels like a needless deviation.
all i can say is:
bash-4.4$
On Sat, Dec 09, 2017 at 11:10:03AM -0700, Theo de Raadt wrote:
> > the default prompt works exactly because it doesn;t try to second guess
> > what the user wants, or what is or isn;t good for them. the mechanism
> > for changing the prompt is trivial.
> >
> > i don;t think it makes sense to chang
On Sat, Dec 09, 2017 at 06:44:44PM +0100, Theo Buehler wrote:
> This was discussed in a smaller circle and has been in snaps for two
> days, but I'd like to show this to a wider audience.
>
> Theo asked me to make sure that all our shells print a prompt including
> the hostname by default. The rea
> the default prompt works exactly because it doesn;t try to second guess
> what the user wants, or what is or isn;t good for them. the mechanism
> for changing the prompt is trivial.
>
> i don;t think it makes sense to change the shells in this way.
Having seen bug reports with data from the wro
On Sat, Dec 09, 2017 at 06:44:44PM +0100, Theo Buehler wrote:
> This was discussed in a smaller circle and has been in snaps for two
> days, but I'd like to show this to a wider audience.
>
> Theo asked me to make sure that all our shells print a prompt including
> the hostname by default. The rea
Sat, 9 Dec 2017 18:44:44 +0100 Theo Buehler
> This was discussed in a smaller circle and has been in snaps for two
> days, but I'd like to show this to a wider audience.
>
> Theo asked me to make sure that all our shells print a prompt including
> the hostname by default. The reasoning is roughly
This was discussed in a smaller circle and has been in snaps for two
days, but I'd like to show this to a wider audience.
Theo asked me to make sure that all our shells print a prompt including
the hostname by default. The reasoning is roughly as follows:
With tmux, ssh and vmd, we tend to open s
20 matches
Mail list logo
