#713 User command prefixed with UNC path

[daleif]

On a Domain controlled Win7, where the users Documents folder is transparently mapped to a network path (UNC path) on a file server, there seem to be a problem when adding user commands. We wanted to add makeglossaries. We added

makeglossaries %

as user0

But every time we try to execute it we get the same error

'\\host\path\path' CMD.EXE was stared with the above path as the current directory. UNC paths are not supported....

ANd then a failure, because CMD drops into some random folder and of course the files we'd like to treat are not in there.

Shouldn't the folder prefix to CMD.EXE be a local folder instead?

AFAIK the Domain controlled folders have a local folder path (V:\whatever) and a corresponding UNC path.

Though I have no idea how to access the local folder name (I usually do not work on Windows, is just reporting the problem)

/daleif

[Benito van der Zander]

I do not think texstudio involves cmd.exe when calling a program.

Perhaps makeglossaries itself tries to launch cmd.exe

You could just map the network path to a drive in explorer.

edit: fixed typo

[daleif]

That will not explain why makeglossaries works perfectly when used from the commandline

Sent from my Android phone using TouchDown (www.nitrodesk.com)

-----Original Message-----
From: Benito van der Zander [benibela@users.sf.net]
Received: torsdag, 18 apr. 2013, 18:28
To: [texstudio:bugs] [713@bugs.texstudio.p.re.sf.net]
Subject: [texstudio:bugs] #713 Use rcommand prefixed with UNC path

I do not thing texstudio involves cmd.exe when calling a program.

Perhaps makeglossaries itself tries to launch cmd.exe

You could just map the network path to a drive in explorer

---

[bugs:#713]http://sourceforge.net/p/texstudio/bugs/713/ Use rcommand prefixed with UNC path

Status: open
Created: Wed Apr 17, 2013 09:44 AM UTC by daleif
Last Updated: Wed Apr 17, 2013 09:44 AM UTC
Owner: nobody

On a Domain controlled Win7, where the users Documents folder is transparently mapped to a network path (UNC path) on a file server, there seem to be a problem when adding user commands. We wanted to add makeglossaries. We added

makeglossaries %

as user0

But every time we try to execute it we get the same error

'\host\path\path' CMD.EXE was stared with the above path as the current directory. UNC paths are not supported....

ANd then a failure, because CMD drops into some random folder and of course the files we'd like to treat are not in there.

Shouldn't the folder prefix to CMD.EXE be a local folder instead?

AFAIK the Domain controlled folders have a local folder path (V:\whatever) and a corresponding UNC path.

Though I have no idea how to access the local folder name (I usually do not work on Windows, is just reporting the problem)

/daleif

---

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/texstudio/bugs/713/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

[Tim Hoffmann]

Does the command work when you run makeglossaries from the command line?

[daleif]

Works perfectly. That's why we suspected the user command did something strange.

Sent from my Android phone using TouchDown (www.nitrodesk.com)

-----Original Message-----
From: Tim Hoffmann [t_hoffmann@users.sf.net]
Received: torsdag, 18 apr. 2013, 20:03
To: [texstudio:bugs] [713@bugs.texstudio.p.re.sf.net]
Subject: [texstudio:bugs] #713 Use rcommand prefixed with UNC path

Does the command work when you run makeglossaries from the command line?

---

[bugs:#713]http://sourceforge.net/p/texstudio/bugs/713/ Use rcommand prefixed with UNC path

Status: open
Created: Wed Apr 17, 2013 09:44 AM UTC by daleif
Last Updated: Thu Apr 18, 2013 04:28 PM UTC
Owner: nobody

On a Domain controlled Win7, where the users Documents folder is transparently mapped to a network path (UNC path) on a file server, there seem to be a problem when adding user commands. We wanted to add makeglossaries. We added

makeglossaries %

as user0

But every time we try to execute it we get the same error

'\host\path\path' CMD.EXE was stared with the above path as the current directory. UNC paths are not supported....

ANd then a failure, because CMD drops into some random folder and of course the files we'd like to treat are not in there.

Shouldn't the folder prefix to CMD.EXE be a local folder instead?

AFAIK the Domain controlled folders have a local folder path (V:\whatever) and a corresponding UNC path.

Though I have no idea how to access the local folder name (I usually do not work on Windows, is just reporting the problem)

/daleif

---

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/texstudio/bugs/713/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

[Benito van der Zander]

How are you even running it on the command line?

I though cmd.exe does not support unc paths

[daleif]

Note that the system is setup with folder redirection. Thus the users documents folder is redirected onto a unc path.

Are noget starting ts in a folder that looks like a unc path. In windows the folder looks like it is a part of a normal drive.

So I'm wondering where that unc path comes into the picture.

Sent from my Android phone using TouchDown (www.nitrodesk.com)

-----Original Message-----
From: Benito van der Zander [benibela@users.sf.net]
Received: torsdag, 18 apr. 2013, 18:28
To: [texstudio:bugs] [713@bugs.texstudio.p.re.sf.net]
Subject: [texstudio:bugs] #713 Use rcommand prefixed with UNC path

I do not thing texstudio involves cmd.exe when calling a program.

Perhaps makeglossaries itself tries to launch cmd.exe

You could just map the network path to a drive in explorer

---

[bugs:#713]http://sourceforge.net/p/texstudio/bugs/713/ Use rcommand prefixed with UNC path

Status: open
Created: Wed Apr 17, 2013 09:44 AM UTC by daleif
Last Updated: Wed Apr 17, 2013 09:44 AM UTC
Owner: nobody

On a Domain controlled Win7, where the users Documents folder is transparently mapped to a network path (UNC path) on a file server, there seem to be a problem when adding user commands. We wanted to add makeglossaries. We added

makeglossaries %

as user0

But every time we try to execute it we get the same error

'\host\path\path' CMD.EXE was stared with the above path as the current directory. UNC paths are not supported....

ANd then a failure, because CMD drops into some random folder and of course the files we'd like to treat are not in there.

Shouldn't the folder prefix to CMD.EXE be a local folder instead?

AFAIK the Domain controlled folders have a local folder path (V:\whatever) and a corresponding UNC path.

Though I have no idea how to access the local folder name (I usually do not work on Windows, is just reporting the problem)

/daleif

---

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/texstudio/bugs/713/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

[daleif]

See my other answer. The folder we are running in is redirected to a unc path. So the cli runs via a drive letter, but apparently ts is not when it is calling the command.

I'm wondering, how is the user command actually called from within ts? Makeglossaries is a cli programme, so I'm guessing ts is calling it via a shell of some sorts, but how?

Sent from my Android phone using TouchDown (www.nitrodesk.com)

-----Original Message-----
From: Benito van der Zander [benibela@users.sf.net]
Received: torsdag, 18 apr. 2013, 20:46
To: [texstudio:bugs] [713@bugs.texstudio.p.re.sf.net]
Subject: [texstudio:bugs] #713 Use rcommand prefixed with UNC path

How are you even running it on the command line?

I though cmd.exe does not support unc paths

---

[bugs:#713]http://sourceforge.net/p/texstudio/bugs/713/ Use rcommand prefixed with UNC path

Status: open
Created: Wed Apr 17, 2013 09:44 AM UTC by daleif
Last Updated: Thu Apr 18, 2013 06:03 PM UTC
Owner: nobody

On a Domain controlled Win7, where the users Documents folder is transparently mapped to a network path (UNC path) on a file server, there seem to be a problem when adding user commands. We wanted to add makeglossaries. We added

makeglossaries %

as user0

But every time we try to execute it we get the same error

'\host\path\path' CMD.EXE was stared with the above path as the current directory. UNC paths are not supported....

ANd then a failure, because CMD drops into some random folder and of course the files we'd like to treat are not in there.

Shouldn't the folder prefix to CMD.EXE be a local folder instead?

AFAIK the Domain controlled folders have a local folder path (V:\whatever) and a corresponding UNC path.

Though I have no idea how to access the local folder name (I usually do not work on Windows, is just reporting the problem)

/daleif

---

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/texstudio/bugs/713/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

[Tim Hoffmann]

The issue is the following:

TXS will runs all commands with the path of the tex file as working directory. If you open a file from a UNC location, the working directory will be a UNC path. Since makeglossaries internally calls cmd and since this does not support UNC working directories, this causes the error.

Workaround:

It may not be obvious if the path you supply when opening via User Documents is local or UNC, because windows obscures the actual storage location. However, the path is displayed in the TXS title bar.

1. Map a network drive to the UNC path of your User Documents folder.
   e.g. net use z:\ \\host\path (or via explorer)

2. Open the file via the drive letter in TXS (z:\subPath\your.tex)

3. Now it should work.

[Denis Bitouzé]

Is this trouble related to the one I reported on TeX Live list and on makeglossaries bug tracker?

[Tim Hoffmann]

Not directly. This one here is because cmd.exe does not support UNC paths as working directory.

Yours might be related to Unicode shortcomings of cmd.exe (just a guess), but it doesn't have anything to do with UNC paths.

[daleif]

I'm not sure. The user did not have a long user name or any accents in it. But they may very well be related somehow

/Lars Madsen
Institut for Matematik / Department of Mathematics
Aarhus Universitet / Aarhus University
Mere info: http://au.dk/daleif@imf / More information: http://au.dk/en/daleif@imf

---

From: "Denis Bitouzé" [denisbitouze@users.sf.net]
Sent: 25 April 2013 09:44
To: [texstudio:bugs]
Subject: [texstudio:bugs] Re: #713 User command prefixed with UNC path

Is this trouble related to the one I reported on TeX Live listhttp://tug.org/pipermail/tex-live/2013-April/033252.html and on makeglossaries bug trackerhttp://www.dickimaw-books.com/cgi-bin/bugtracker.cgi?action=view&category=All&status=All&search_string=&key=21?

---

[bugs:#713]http://sourceforge.net/p/texstudio/bugs/713/ User command prefixed with UNC path

Status: open
Created: Wed Apr 17, 2013 09:44 AM UTC by daleif
Last Updated: Wed Apr 24, 2013 11:44 PM UTC
Owner: nobody

On a Domain controlled Win7, where the users Documents folder is transparently mapped to a network path (UNC path) on a file server, there seem to be a problem when adding user commands. We wanted to add makeglossaries. We added

makeglossaries %

as user0

But every time we try to execute it we get the same error

'\host\path\path' CMD.EXE was stared with the above path as the current directory. UNC paths are not supported....

ANd then a failure, because CMD drops into some random folder and of course the files we'd like to treat are not in there.

Shouldn't the folder prefix to CMD.EXE be a local folder instead?

AFAIK the Domain controlled folders have a local folder path (V:\whatever) and a corresponding UNC path.

Though I have no idea how to access the local folder name (I usually do not work on Windows, is just reporting the problem)

/daleif

---

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/texstudio/bugs/713/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

[Denis Bitouzé]

What's the TeX distribution used by this user: MiKTeX or TeX Live?

[daleif]

It is not the case, the files are already on a folder which is transparently redirected onto a UNC network path.

To me it seems as if the command used to get the current directory is not returning the local drive path.

(can I find what you are doing somewhere?)

/Lars Madsen
Institut for Matematik / Department of Mathematics
Aarhus Universitet / Aarhus University
Mere info: http://au.dk/daleif@imf / More information: http://au.dk/en/daleif@imf

---

From: Tim Hoffmann [t_hoffmann@users.sf.net]
Sent: 25 April 2013 01:42
To: [texstudio:bugs]
Subject: [texstudio:bugs] #713 Use rcommand prefixed with UNC path

The issue is the following:

TXS will runs all commands with the path of the tex file as working directory. If you open a file from a UNC location, the working directory will be a UNC path. Since makeglossaries internally calls cmd and since this does not support UNC working directories, this causes the error.

Workaround:

It may not be obvious if the path you supply when opening via User Documents is local or , because windows obscures the actual storage location. However, the path is displayed in the TXS title bar.

1. Map a network drive to the UNC path of your User Documents folder.
   e.g. net use z:\ \host\path (or via explorer)

2. Open the file via the drive letter in TXS (z:\subPath\your.tex)

3. Now it should work.

---

[bugs:#713]http://sourceforge.net/p/texstudio/bugs/713/ Use rcommand prefixed with UNC path

Status: open
Created: Wed Apr 17, 2013 09:44 AM UTC by daleif
Last Updated: Thu Apr 18, 2013 06:46 PM UTC
Owner: nobody

On a Domain controlled Win7, where the users Documents folder is transparently mapped to a network path (UNC path) on a file server, there seem to be a problem when adding user commands. We wanted to add makeglossaries. We added

makeglossaries %

as user0

But every time we try to execute it we get the same error

'\host\path\path' CMD.EXE was stared with the above path as the current directory. UNC paths are not supported....

ANd then a failure, because CMD drops into some random folder and of course the files we'd like to treat are not in there.

Shouldn't the folder prefix to CMD.EXE be a local folder instead?

AFAIK the Domain controlled folders have a local folder path (V:\whatever) and a corresponding UNC path.

Though I have no idea how to access the local folder name (I usually do not work on Windows, is just reporting the problem)

/daleif

---

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/texstudio/bugs/713/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

[daleif]

tex live (we recommend TL for all users)

/Lars Madsen
Institut for Matematik / Department of Mathematics
Aarhus Universitet / Aarhus University
Mere info: http://au.dk/daleif@imf / More information: http://au.dk/en/daleif@imf

---

From: "Denis Bitouzé" [denisbitouze@users.sf.net]
Sent: 25 April 2013 10:03
To: [texstudio:bugs]
Subject: [texstudio:bugs] #713 User command prefixed with UNC path

What's the TeX distribution used by this user: MiKTeX or TeX Live?

---

[bugs:#713]http://sourceforge.net/p/texstudio/bugs/713/ User command prefixed with UNC path

Status: open
Created: Wed Apr 17, 2013 09:44 AM UTC by daleif
Last Updated: Wed Apr 24, 2013 11:44 PM UTC
Owner: nobody

On a Domain controlled Win7, where the users Documents folder is transparently mapped to a network path (UNC path) on a file server, there seem to be a problem when adding user commands. We wanted to add makeglossaries. We added

makeglossaries %

as user0

But every time we try to execute it we get the same error

'\host\path\path' CMD.EXE was stared with the above path as the current directory. UNC paths are not supported....

ANd then a failure, because CMD drops into some random folder and of course the files we'd like to treat are not in there.

Shouldn't the folder prefix to CMD.EXE be a local folder instead?

AFAIK the Domain controlled folders have a local folder path (V:\whatever) and a corresponding UNC path.

Though I have no idea how to access the local folder name (I usually do not work on Windows, is just reporting the problem)

/daleif

---

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/texstudio/bugs/713/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

[Denis Bitouzé]

tex live

Okay.

(we recommend TL for all users)

So am I :) But it could be interesting to know if the trouble arises with a TeX distribution dedicated to Windows.

[daleif]

I just did an interesting observation. Did a test that I sometimes do on Linux when people have been messing with PATHs in a 'bad' way.

(1) If I start texstudio by double clicking on the tex file, I get the UNC path error when I try a user command

However

(2) If I start it from the command line via

"c:\Programme Files (x86)\texstudio\texstudio.exe" file.tex

then the user command works just fine.

So to me it seems the command you are calling to get the folder where file.tex is located, might not be robust in all cases.

/Lars Madsen
Institut for Matematik / Department of Mathematics
Aarhus Universitet / Aarhus University
Mere info: http://au.dk/daleif@imf / More information: http://au.dk/en/daleif@imf

---

From: Tim Hoffmann [t_hoffmann@users.sf.net]
Sent: 25 April 2013 01:42
To: [texstudio:bugs]
Subject: [texstudio:bugs] #713 Use rcommand prefixed with UNC path

The issue is the following:

TXS will runs all commands with the path of the tex file as working directory. If you open a file from a UNC location, the working directory will be a UNC path. Since makeglossaries internally calls cmd and since this does not support UNC working directories, this causes the error.

Workaround:

It may not be obvious if the path you supply when opening via User Documents is local or , because windows obscures the actual storage location. However, the path is displayed in the TXS title bar.

1. Map a network drive to the UNC path of your User Documents folder.
   e.g. net use z:\ \host\path (or via explorer)

2. Open the file via the drive letter in TXS (z:\subPath\your.tex)

3. Now it should work.

---

[bugs:#713]http://sourceforge.net/p/texstudio/bugs/713/ Use rcommand prefixed with UNC path

Status: open
Created: Wed Apr 17, 2013 09:44 AM UTC by daleif
Last Updated: Thu Apr 18, 2013 06:46 PM UTC
Owner: nobody

On a Domain controlled Win7, where the users Documents folder is transparently mapped to a network path (UNC path) on a file server, there seem to be a problem when adding user commands. We wanted to add makeglossaries. We added

makeglossaries %

as user0

But every time we try to execute it we get the same error

'\host\path\path' CMD.EXE was stared with the above path as the current directory. UNC paths are not supported....

ANd then a failure, because CMD drops into some random folder and of course the files we'd like to treat are not in there.

Shouldn't the folder prefix to CMD.EXE be a local folder instead?

AFAIK the Domain controlled folders have a local folder path (V:\whatever) and a corresponding UNC path.

Though I have no idea how to access the local folder name (I usually do not work on Windows, is just reporting the problem)

/daleif

---

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/texstudio/bugs/713/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

[daleif]

Just realised, there are three ways to open a file:

(1) Double click a .tex file
(2) Command line
(3) Start TSX and navigate to the file via 'Open file'

(2) and (3) works fine, no problem at all.

(1) seem to receive the wrong information

/Lars Madsen
Institut for Matematik / Department of Mathematics
Aarhus Universitet / Aarhus University
Mere info: http://au.dk/daleif@imf / More information: http://au.dk/en/daleif@imf

---

From: daleif [daleif@users.sf.net]
Sent: 25 April 2013 10:22
To: [texstudio:bugs]
Subject: [texstudio:bugs] Re: #713 User command prefixed with UNC path

I just did an interesting observation. Did a test that I sometimes do on Linux when people have been messing with PATHs in a 'bad' way.

(1) If I start texstudio by double clicking on the tex file, I get the UNC path error when I try a user command

However

(2) If I start it from the command line via

"c:\Programme Files (x86)\texstudio\texstudio.exe" file.tex

then the user command works just fine.

So to me it seems the command you are calling to get the folder where file.tex is located, might not be robust in all cases.

/Lars Madsen
Institut for Matematik / Department of Mathematics
Aarhus Universitet / Aarhus University
Mere info: http://au.dk/daleif@imf / More information: http://au.dk/en/daleif@imf

---

From: Tim Hoffmann [t_hoffmann@users.sf.net]
Sent: 25 April 2013 01:42
To: [texstudio:bugs]
Subject: [texstudio:bugs] #713 Use rcommand prefixed with UNC path

The issue is the following:

TXS will runs all commands with the path of the tex file as working directory. If you open a file from a UNC location, the working directory will be a UNC path. Since makeglossaries internally calls cmd and since this does not support UNC working directories, this causes the error.

Workaround:

It may not be obvious if the path you supply when opening via User Documents is local or , because windows obscures the actual storage location. However, the path is displayed in the TXS title bar.

1. Map a network drive to the UNC path of your User Documents folder.
   e.g. net use z:\ \host\path (or via explorer)

2. Open the file via the drive letter in TXS (z:\subPath\your.tex)

3. Now it should work.

---

[bugs:#713]http://sourceforge.net/p/texstudio/bugs/713/http://sourceforge.net/p/texstudio/bugs/713/ Use rcommand prefixed with UNC path

Status: open
Created: Wed Apr 17, 2013 09:44 AM UTC by daleif
Last Updated: Thu Apr 18, 2013 06:46 PM UTC
Owner: nobody

On a Domain controlled Win7, where the users Documents folder is transparently mapped to a network path (UNC path) on a file server, there seem to be a problem when adding user commands. We wanted to add makeglossaries. We added

makeglossaries %

as user0

But every time we try to execute it we get the same error

'\host\path\path' CMD.EXE was stared with the above path as the current directory. UNC paths are not supported....

ANd then a failure, because CMD drops into some random folder and of course the files we'd like to treat are not in there.

Shouldn't the folder prefix to CMD.EXE be a local folder instead?

AFAIK the Domain controlled folders have a local folder path (V:\whatever) and a corresponding UNC path.

Though I have no idea how to access the local folder name (I usually do not work on Windows, is just reporting the problem)

/daleif

---

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/texstudio/bugs/713/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

---

[bugs:#713]http://sourceforge.net/p/texstudio/bugs/713/ User command prefixed with UNC path

Status: open
Created: Wed Apr 17, 2013 09:44 AM UTC by daleif
Last Updated: Thu Apr 25, 2013 08:03 AM UTC
Owner: nobody

On a Domain controlled Win7, where the users Documents folder is transparently mapped to a network path (UNC path) on a file server, there seem to be a problem when adding user commands. We wanted to add makeglossaries. We added

makeglossaries %

as user0

But every time we try to execute it we get the same error

'\host\path\path' CMD.EXE was stared with the above path as the current directory. UNC paths are not supported....

ANd then a failure, because CMD drops into some random folder and of course the files we'd like to treat are not in there.

Shouldn't the folder prefix to CMD.EXE be a local folder instead?

AFAIK the Domain controlled folders have a local folder path (V:\whatever) and a corresponding UNC path.

Though I have no idea how to access the local folder name (I usually do not work on Windows, is just reporting the problem)

/daleif

---

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/texstudio/bugs/713/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

[Tim Hoffmann]

It is not the case, the files are already on a folder which is transparently redirected onto a UNC network path.

To me it seems as if the command used to get the current directory is not returning the local drive path.

(can I find what you are doing somewhere?)

TXS can just uses the file path, as it is provided. As said, you can see the path in the title bar.

Just realised, there are three ways to open a file:

(1) Double click a .tex file
(2) Command line
(3) Start TSX and navigate to the file via 'Open file'

(2) and (3) works fine, no problem at all.

(1) seem to receive the wrong information

Apparently windows gives the path differently depending on the way you open the file. There is nothing we can do about this in TXS because it's already happening on the OS side.

Btw.: Please quote only relevant parts of a message, otherwise the thread becomes very hard to read.

[daleif]

Sorry about the quoting, I do not like it either, but that is the Exchange way.

I'll ask around to see if there is a way around this problem path problem

Sent from my Android phone using TouchDown (www.nitrodesk.com)

-----Original Message-----
From: Tim Hoffmann [t_hoffmann@users.sf.net]
Received: torsdag, 25 apr. 2013, 20:53
To: [texstudio:bugs] [713@bugs.texstudio.p.re.sf.net]
Subject: [texstudio:bugs] #713 User command prefixed with UNC path

It is not the case, the files are already on a folder which is transparently redirected onto a UNC network path.

To me it seems as if the command used to get the current directory is not returning the local drive path.

(can I find what you are doing somewhere?)

TXS can just uses the file path, as it is provided. As said, you can see the path in the title bar.

Just realised, there are three ways to open a file:

(1) Double click a .tex file
(2) Command line
(3) Start TSX and navigate to the file via 'Open file'

(2) and (3) works fine, no problem at all.

(1) seem to receive the wrong information

Apparently windows gives the path differently depending on the way you open the file. There is nothing we can do about this in TXS because it's already happening on the OS side.

Btw.: Please quote only relevant parts of a message, otherwise the thread becomes very hard to read.

---

[bugs:#713]http://sourceforge.net/p/texstudio/bugs/713/ User command prefixed with UNC path

Status: open
Created: Wed Apr 17, 2013 09:44 AM UTC by daleif
Last Updated: Thu Apr 25, 2013 08:16 AM UTC
Owner: nobody

On a Domain controlled Win7, where the users Documents folder is transparently mapped to a network path (UNC path) on a file server, there seem to be a problem when adding user commands. We wanted to add makeglossaries. We added

makeglossaries %

as user0

But every time we try to execute it we get the same error

'\host\path\path' CMD.EXE was stared with the above path as the current directory. UNC paths are not supported....

ANd then a failure, because CMD drops into some random folder and of course the files we'd like to treat are not in there.

Shouldn't the folder prefix to CMD.EXE be a local folder instead?

AFAIK the Domain controlled folders have a local folder path (V:\whatever) and a corresponding UNC path.

Though I have no idea how to access the local folder name (I usually do not work on Windows, is just reporting the problem)

/daleif

---

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/texstudio/bugs/713/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

[daleif]

Sorry about the quoting, I do not like it either, but that is the Exchange way.

I'll ask around to see if there is a way around this problem path problem

Sent from my Android phone using TouchDown (www.nitrodesk.com)

-----Original Message-----
From: Tim Hoffmann [t_hoffmann@users.sf.net]
Received: torsdag, 25 apr. 2013, 20:53
To: [texstudio:bugs] [713@bugs.texstudio.p.re.sf.net]
Subject: [texstudio:bugs] #713 User command prefixed with UNC path

It is not the case, the files are already on a folder which is transparently redirected onto a UNC network path.

To me it seems as if the command used to get the current directory is not returning the local drive path.

(can I find what you are doing somewhere?)

TXS can just uses the file path, as it is provided. As said, you can see the path in the title bar.

Just realised, there are three ways to open a file:

(1) Double click a .tex file
(2) Command line
(3) Start TSX and navigate to the file via 'Open file'

(2) and (3) works fine, no problem at all.

(1) seem to receive the wrong information

Apparently windows gives the path differently depending on the way you open the file. There is nothing we can do about this in TXS because it's already happening on the OS side.

Btw.: Please quote only relevant parts of a message, otherwise the thread becomes very hard to read.

---

[bugs:#713]http://sourceforge.net/p/texstudio/bugs/713/ User command prefixed with UNC path

Status: open
Created: Wed Apr 17, 2013 09:44 AM UTC by daleif
Last Updated: Thu Apr 25, 2013 08:16 AM UTC
Owner: nobody

On a Domain controlled Win7, where the users Documents folder is transparently mapped to a network path (UNC path) on a file server, there seem to be a problem when adding user commands. We wanted to add makeglossaries. We added

makeglossaries %

as user0

But every time we try to execute it we get the same error

'\host\path\path' CMD.EXE was stared with the above path as the current directory. UNC paths are not supported....

ANd then a failure, because CMD drops into some random folder and of course the files we'd like to treat are not in there.

Shouldn't the folder prefix to CMD.EXE be a local folder instead?

AFAIK the Domain controlled folders have a local folder path (V:\whatever) and a corresponding UNC path.

Though I have no idea how to access the local folder name (I usually do not work on Windows, is just reporting the problem)

/daleif

---

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/texstudio/bugs/713/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

[daleif]

There is no unicode characters involved as far as I can see.

Sent from my Android phone using TouchDown (www.nitrodesk.com)

[daleif]

If one should read the workaround as 'don't doubleclick', then the workaround should work.

The files here are accessed via drive names etc. And only double clicking causes problems.

But I agree, it seems to be an OS issue.

Interestingly, our Windows guys have never heard of this difference in the reported file path.

/Lars Madsen
Institut for Matematik / Department of Mathematics
Aarhus Universitet / Aarhus University
Mere info: http://au.dk/daleif@imf / More information: http://au.dk/en/daleif@imf

---

From: Tim Hoffmann [t_hoffmann@users.sf.net]
Sent: 08 May 2013 00:13
To: [texstudio:bugs]
Subject: [texstudio:bugs] #713 User command prefixed with UNC path

• status: open --> closed

---

[bugs:#713]http://sourceforge.net/p/texstudio/bugs/713/ User command prefixed with UNC path

Status: closed
Created: Wed Apr 17, 2013 09:44 AM UTC by daleif
Last Updated: Thu Apr 25, 2013 06:53 PM UTC
Owner: nobody

On a Domain controlled Win7, where the users Documents folder is transparently mapped to a network path (UNC path) on a file server, there seem to be a problem when adding user commands. We wanted to add makeglossaries. We added

makeglossaries %

as user0

But every time we try to execute it we get the same error

'\host\path\path' CMD.EXE was stared with the above path as the current directory. UNC paths are not supported....

ANd then a failure, because CMD drops into some random folder and of course the files we'd like to treat are not in there.

Shouldn't the folder prefix to CMD.EXE be a local folder instead?

AFAIK the Domain controlled folders have a local folder path (V:\whatever) and a corresponding UNC path.

Though I have no idea how to access the local folder name (I usually do not work on Windows, is just reporting the problem)

/daleif

---

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/texstudio/bugs/713/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

[Tim Hoffmann]

If one should read the workaround as 'don't doubleclick', then the workaround should work.

Double clicking in your Documents folder will not work (and cannot be made to from our side).

The workaround is mapping a drive letter, say z: to the UNC Path corresponding to your Documents folder. Then you can use z:\ instead of documents. From there it works.