cope with GNU groff's incapability to properly escape [] chars
This commit is contained in:
parent
4f8d5a47a4
commit
daf9f30b2f
4
ksh.1tbl
4
ksh.1tbl
@ -1,4 +1,4 @@
|
||||
.\" $MirBSD: ksh.1tbl,v 1.22 2004/04/27 19:59:55 tg Exp $
|
||||
.\" $MirBSD: ksh.1tbl,v 1.23 2004/04/29 19:06:24 tg Exp $
|
||||
.\" $OpenBSD: ksh.1tbl,v 1.65 2004/01/23 23:08:45 jmc Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1980, 1990, 1993
|
||||
@ -4471,7 +4471,7 @@ as its prefix, a bell character is output (usually causing a beep to be
|
||||
sounded).
|
||||
Currently being considered a bug in
|
||||
.Nm ,
|
||||
if the file name contains \[ or \], it cannot be completed, even if
|
||||
if the file name contains \fB[\fR or \fB]\fR, it cannot be completed, even if
|
||||
the character is escaped, in \fBemacs\fR mode.
|
||||
This surprisingly works in \fBvi\fR mode; please submit a fix.
|
||||
.It Ic complete-command ^X^[
|
||||
|
Loading…
x
Reference in New Issue
Block a user