When SHELL BUILTIN COMMANDS section from bash.1 is included into
builtins.1, references to other sections in bash.1 become invalid.
This patch adds conditions to make those references refer
to bash(1) in case builtins.1 man page is viewed.
Signed-off-by: Nikola Forró
---
I've updated the patch t
On Tue, Jan 31, 2017 at 10:13:46AM +0800, ? Dan Jacobson wrote:
> However on slower systems, at the end of the day when the user issues
> the poweroff(8) command, all this might not complete, resulting in the
> entire day's of history getting thrown away.
I'm confused. You don't logout be
Chet Ramey wrote:
> On 1/24/17 2:07 AM, Brian 'geeknik' Carpenter wrote:
> > Going through some ancient bug reports and I came across
> > https://savannah.gnu.org/support/index.php?108884 which apparently nobody
> > uses anymore.
> >
> > <<$(()())|>_[$($(<<0)) crashes bash on Debian, Red Hat, Free
GW> I'm confused. You don't logout before shutting down your computer?
GW> I would strongly recommend doing so, unless it's an emergency.
All I know is I want to issue one command to turn off the computer.
If I logged off first, how could I issue that (poweroff(8)) command?
OK you people turn of
On Wed, Feb 01, 2017 at 03:13:45AM +0800, ? Dan Jacobson wrote:
> GW> I'm confused. You don't logout before shutting down your computer?
> GW> I would strongly recommend doing so, unless it's an emergency.
>
> All I know is I want to issue one command to turn off the computer.
> If I logg
On Wed, Feb 01, 2017 at 03:31:57AM +0800, ? Dan Jacobson wrote:
> GW> Log out, log back in as root, issue the command, and accept that root's
> GW> (very short) shell history will be lost.
>
> Well mention that on the man page.
> I.e., the man page should address the paradox of saving a co
GW> Log out, log back in as root, issue the command, and accept that root's
GW> (very short) shell history will be lost.
Well mention that on the man page.
I.e., the man page should address the paradox of saving a complete
history vs. being able to turn off one's computer.
This is discussed a bit here, along with a common pain point for
tmux/screen users:
https://news.ycombinator.com/item?id=10164053
zsh gets around both issues with a variety of options to have a synchronous
and interleaved history file.
-Jonathan Hankins
On Tue, Jan 31, 2017 at 1:40 PM Greg Wool
