Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com To: cygwin-developers AT cygwin DOT com Subject: Re: New output from mount.exe References: <200104020509 DOT BAA07712 AT envy DOT delorie DOT com> <20010402094800 DOT B956 AT cygbert DOT vinschen DOT de> <20010402110045 DOT B1000 AT redhat DOT com> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII From: Kazuhiro Fujieda Date: 04 Apr 2001 10:32:49 +0900 In-Reply-To: Christopher Faylor's message of Mon, 2 Apr 2001 11:00:45 -0400 Message-ID: Lines: 21 X-Mailer: Gnus v5.3/Emacs 19.34 >>> On Mon, 2 Apr 2001 11:00:45 -0400 >>> Christopher Faylor said: > Again, this was not the rationale for this change. Here is the change > to mount.exe: > > - const char *format = "%-18s %-18s %-11s %s\n"; > + const char *format = "%s on %s type %s (%s)\n"; > > I didn't reformat slashes or do anything else that was not in the > original version of mount. Would you like to go a step further? Corinna's idea "just printing slashes" can reduce chances for newbies to fail to escape backslashes on creating a new entry with the `mount' command. This would be fine. ____ | AIST Kazuhiro Fujieda | HOKURIKU School of Information Science o_/ 1990 Japan Advanced Institute of Science and Technology