From: Ian Roxborough <irox@redhat.com>
To: D-Man <dsh8290@rit.edu>
Cc: sourcenav@sources.redhat.com
Subject: Re: sourcenav munges my preferences!
Date: Fri, 23 Mar 2001 12:55:00 -0000 [thread overview]
Message-ID: <3ABBB83E.6D5CB334@redhat.com> (raw)
In-Reply-To: <20010323103431.D10980@harmony.cs.rit.edu>
This bit really bugs me.
You could try and double up the "/" i.e. "//".
Hopefullt it's gone now but, they where some
dialogs where you had to replace each slash with
four (i.e. "C:\\\\hello\\\\world\\\\test.c").
Ian.
D-Man wrote:
>
> In the preferences dialog I want the build command to be:
>
> sourcenav-ant.bat VSS/LegacyIntegrator buildFull
>
> but snav insists on changing it to
>
> sourcenav-ant.bat VSS\LegacyIntegrator buildFull
>
> I took a look at the source, in multimake.tcl line 215 is :
>
> @@set $this-makecommand [file nativename $sn_options(both,make-command)]
>
> Apparently SNav is trying to be smart by converting paths to the
> native format. The problem is I don't want that. It won't work with
> a '\'. (The build command invokes bash, which runs a shell script
> that runs ant (a make replacement for java) and the shell script needs
> the / because the \L turns into L and the resulting path DNE).
>
> I changed the line to :
>
> @@set $this-makecommand $sn_options(both,make-command)
>
> and the build window now appears correctly. However, if I open the
> preferences dialog again, it has munged the command.
>
> What can I hack to remove this "feature" and get the string exactly as
> I entered?
>
> Thanks,
> -D
prev parent reply other threads:[~2001-03-23 12:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-23 7:34 D-Man
2001-03-23 8:42 ` Chad Bryant
2001-03-23 12:22 ` Unsubscribing.... " Ian Roxborough
2001-03-23 16:04 ` Mo DeJong
2001-03-23 12:55 ` Ian Roxborough [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3ABBB83E.6D5CB334@redhat.com \
--to=irox@redhat.com \
--cc=dsh8290@rit.edu \
--cc=sourcenav@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).