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 Date: Tue, 3 Apr 2001 21:46:09 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: New output from mount.exe Message-ID: <20010403214609.C3112@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: ; from fujieda@jaist.ac.jp on Wed, Apr 04, 2001 at 10:32:49AM +0900 On Wed, Apr 04, 2001 at 10:32:49AM +0900, Kazuhiro Fujieda wrote: >>>> 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. It would also lie to the user about what was happening in the Cygwin internals. Cygwin stores these paths as c:\foo not c:/foo. I don't see any reason to mislead anyone about what Cygwin is really doing. cgf