From: Andy Wong <andywong1981@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: mtxrun --noquotes on windows
Date: Fri, 10 Apr 2009 15:20:17 -0500 [thread overview]
Message-ID: <bf0ab5a50904101320x6f92cadoc8666d15f0de6c8d@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.0904101542270.18385@ybpnyubfg.ybpnyqbznva>
[-- Attachment #1.1: Type: text/plain, Size: 4134 bytes --]
Yes, if leave a space between the last two quotes, mtx output seems ok.
MTXrun |
MTXrun | executing: vim -u NONE -c "set tabstop=8" "test.tex"
MTXrun |
But it still cause vim open two file named "tabstop=8" and "test.tex" to
edit. So it seems vim treat tabstop=8 as a file? that still a quotes
problem, right? I also test if there no space in quoted arguments, such as
mtxrun --noquotes bin:vim "-u NONE -c \"help\" \"test.tex\" "
This time vim will open the "test.tex" and help window as expected. If any
command with space in -c parameter, vim can not correct executed.
manually execute the vim command:
vim -u NONE -c "set tabstop=8" "test.tex"
vim open the "test.tex" only to edit as expected.
Andy
On Fri, Apr 10, 2009 at 2:49 PM, Aditya Mahajan <adityam@umich.edu> wrote:
> On Fri, 10 Apr 2009, Andy Wong wrote:
>
> I think I may not write it clear in my previous email. I run the command as
>>
>> mtxrun --noquotes bin:vim "-u NONE -c \"set tabstop=8\" \"test.tex\""
>>
>
> If you quote the filename, then it should be
>
mtxrun --noquotes bin:vim "-u NONE -c \"set tabstop=8\" \"test.tex\" "
>
> Notice the space before the last quote. This will open two files test.tex
> and "", but that it is ok. The last file is ignored by t-vim.
>
> which got the mtxrun output has spurious " before test.tex. if omit the \"
>> around the test.tex, like this,
>>
>> mtxrun --noquotes bin:vim "-u NONE -c \"set tabstop=8\" test.tex"
>>
>> there are no spurious " in mtxrun output.
>>
>
> So it is not mtxrun's fault.
>
> However, both will make vim open a
>> new file named "tabset=8"
>>
>
> You mean tabstop=8?
>
> and the test.tex to be edited. That is the
>> problem. I guess under linux this command should open vim to edit the
>> test.tex only instead.
>>
>
> If vim is passed the correct command, I do not see why it should not
> execute it in the same way in windows. Try one more thing. Run
>
> mtxrun --noquotes bin:vim "-u NONE -c \"set tabstop=8\" \"test.tex\" "
>
> mtxrun should report that it is executing
>
> vim -u NONE -c "set tabstop=8" "test.tex"
>
> Execute the above command manually on the terminal. Do you get the same
> result in both cases?
>
> Aditya
>
>
>
>
> On Fri, Apr 10, 2009 at 1:40 PM, Aditya Mahajan <adityam@umich.edu> wrote:
>>
>> Hi,
>>>
>>> It seems that mtxrun --noquotes behaves differently on windows and linux.
>>> Can someone on windows (who has vim) check the following. Run
>>>
>>> mtxrun --noquotes bin:vim "-u NONE -c \"set tabstop=8\" test.tex"
>>>
>>> You will enter in vim. Press :qa! to exit vim. What does the output on
>>> the
>>> terminal say? On my linux machine, I get
>>>
>>> MTXrun | executing: vim -u NONE -c "set tabstop=8" test.tex
>>>
>>> Andy Wong tested it on windows and he gets
>>>
>>> MTXrun | executing: vim -u NONE -c "set tabstop=8" "test.tex
>>>
>>> Notice the spurious " before test.tex. This causes t-vim to fail on
>>> windows. Do others on windows get the same behavour? I do not see a
>>> reason
>>> why mtxrun should behave differently on linux and windows.
>>>
>>> Thanks,
>>> Aditya
>>>
>>>
>>>
>>> ___________________________________________________________________________________
>>> If your question is of interest to others as well, please add an entry to
>>> the Wiki!
>>>
>>> maillist : ntg-context@ntg.nl /
>>> http://www.ntg.nl/mailman/listinfo/ntg-context
>>> webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
>>> archive : https://foundry.supelec.fr/projects/contextrev/
>>> wiki : http://contextgarden.net
>>>
>>>
>>> ___________________________________________________________________________________
>>>
>>>
>>
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to
> the Wiki!
>
> maillist : ntg-context@ntg.nl /
> http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive : https://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
>
> ___________________________________________________________________________________
>
[-- Attachment #1.2: Type: text/html, Size: 6917 bytes --]
[-- Attachment #2: Type: text/plain, Size: 487 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-04-10 20:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 18:40 Aditya Mahajan
2009-04-10 19:19 ` Andy Wong
2009-04-10 19:49 ` Aditya Mahajan
2009-04-10 20:20 ` Andy Wong [this message]
2009-04-10 20:32 ` Aditya Mahajan
2009-04-10 20:37 ` Andy Wong
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=bf0ab5a50904101320x6f92cadoc8666d15f0de6c8d@mail.gmail.com \
--to=andywong1981@gmail.com \
--cc=ntg-context@ntg.nl \
/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 NNTP newsgroup(s).