Mail Archives: djgpp/2001/03/22/19:16:43
Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:
> On Unix, I understand why does Bash do that. But the DJGPP port
> shouldn't do that, since a colon is routinely used in file names.
> It would be a nuisance to require users to escape the colon after the
> drive letter in each file name they type.
They don't have to actually type it in the DJGPP port of Bash 2.03, it
automatically gets inserted as part of the tab completetion. And this
seems to be the key to getting the space escaped.
The following patch is to restore the feature so that Bash 2.04 behaves
as 2.03 did. Also, I believe it fixes something else too because there
was some DOS specific code that was not being compiled in (line 1840).
--- bashline.c.orig Wed Apr 5 17:48:54 2000
+++ bashline.c Tue Mar 20 17:13:00 2001
@@ -45,6 +45,8 @@
#include <glob/glob.h>
+#include "filesys.h"
+
#ifdef __MSDOS__
#include "dosutil.h"
#endif
@@ -322,7 +324,11 @@
enable_hostname_completion (perform_hostname_completion);
/* characters that need to be quoted when appearing in filenames. */
+#ifndef HAVE_DOS_BASED_FILE_SYSTEM
rl_filename_quote_characters = " \t\n\\\"'@<>=;|&()#$`?*[!:{"; /* { */
+#else
+ rl_filename_quote_characters = " \t\n\\\"'@<>=;|&()#$`?*[!{"; /* { */
+#endif
rl_filename_quoting_function = bash_quote_filename;
rl_filename_dequoting_function = bash_dequote_filename;
rl_char_is_quoted_p = char_is_quoted;
- Raw text -