[R] file path

[Uwe Ligges]

On 09.05.2012 17:14, Wincent wrote:
> Hmm, I don't think it gives what I want.
>
> For example, I assign a file name to f,
>> f<- "a?b.txt"
>> file.path("e:",f)
> [1] "e:/a?b.txt"
>
> The resultant character is not accepted as a file name by Windows OS.


Not on Linux if you write to a smb file system, and that system won't 
tell you in advance. hence you have to know it yourself or correctly 
interpret the corresponding error messages.

Uwe Ligges


> On 9 May 2012 20:32, Tal Galili<tal.galili at gmail.com>  wrote:
>> Hi Wincent,
>> Have a look at:
>> ?file.path
>>
>>
>>
>> ----------------Contact
>> Details:-------------------------------------------------------
>> Contact me: Tal.Galili at gmail.com |  972-52-7275845
>> Read me: www.talgalili.com (Hebrew) | www.biostatistics.co.il (Hebrew) |
>> www.r-statistics.com (English)
>> ----------------------------------------------------------------------------------------------
>>
>>
>>
>>
>> On Wed, May 9, 2012 at 11:03 AM, Wincent<ronggui.huang at gmail.com>  wrote:
>>>
>>> Dear all, is there any function to assert whether a file path is
>>> legitimate, and to convert any potential file path to a legitimate
>>> file path?
>>>
>>> I automate a batch of files and write them to plain text files with
>>> cat(). The file argument of cat() is generated automatically which may
>>> contain characters such as ?<  >, unacceptable in Windows OS. What I
>>> do at this moment is to strip such characters off with gsub(). Is
>>> there any direct way to make legitimate file path without detailed
>>> knowledge about the naming rule specific to a OS?
>>>
>>> Best
>>>
>>> --
>>> Wincent Ronggui HUANG
>>> Sociology Department of Fudan University
>>> PhD of City University of Hong Kong
>>> http://homepage.fudan.edu.cn/rghuang/cv/
>>>
>>> ______________________________________________
>>> R-help at r-project.org mailing list
>>> https://stat.ethz.ch/mailman/listinfo/r-help
>>> PLEASE do read the posting guide
>>> http://www.R-project.org/posting-guide.html
>>> and provide commented, minimal, self-contained, reproducible code.
>>
>>
>
>
>