On 19 Jun 2008, at 12:24 AM, Charilaos Skiadas wrote:
> On Jun 18, 2008, at 6:14 PM, Christiaan Hofman wrote:
>
>>
>> On 18 Jun 2008, at 11:57 PM, Charilaos Skiadas wrote:
>>
>>> On Jun 18, 2008, at 5:37 PM, Christiaan Hofman wrote:
>>>
>>>>
>>>> On 18 Jun 2008, at 11:19 PM, robert coleman wrote:
>>>>
>>>>>
>>>>>> How can I do an inverse search from a skim document made from a
>>>>>> latex
>>>>>> file with \input files? I'm using auctex in aquamacs and
>>>>>> pdfsync. I
>>>>>> have \usepackage{pdfsync} in the preample and command-shift click
>>>>>> only takes me to the master file.
>>>>>
>>>>
>>>> Skim does support pdfsync for multi-file projects. though it
>>>> depends
>>>> on what pdfsync does with it. And I don't know if pdfsync properly
>>>> handles \input, perhaps it only works with \include. So the short
>>>> answer is: this is a question about pdfsync and latex, not Skim. If
>>>> pdfsync can handle it, Skim can, and if pdfsync can't handle it,
>>>> Skim
>>>> can't.
>>>>
>>>> BTW, if you use latex you shouldn't use \input to start with.
>>>> That's
>>>> really bad practice, and if things don't work because of it you
>>>> have
>>>> only yourself to blame (unless you collaborate, than you can blame
>>>> your collaborators).
>>>>
>>>> Christiaan
>>>>
>>>
>>> Actually there's nothing wrong with \input{filename}, it is I
>>> believe
>>> well documented and part of LaTeX, and it differs from \include in
>>> the fact that it does not try a \clearpage. I couldn't find a
>>> reference right now, but I believe that "\input filename" is
>>> actually
>>> a different command, and that is the "TeX" one that one might want
>>> to
>>> avoid, and that's the one that pdfsync definitely does not follow.
>>
>> No, "\command argument" is 100% equivalent to "\command{argument}" as
>> long as the first form makes sense. That's part of the TeX syntax:
>> braces are only used to *force* grouping, they're never required.
>
> Actually no, "\command foo" is equivalent to "\command{f}oo", each
> character of argument will be interpreted as a separate entity.
> That's why for instance \frac12 is the same as \frac{1}{2}.
>
> \input is special in this respect. otherwise, the line "\input
> foo.tex" would have to be interpreted as "\input{f} oo.tex" and would
> try to read a file named f. In general you are correct, that what
> follows \command will be treated as arguments to \command if \command
> takes arguments, but in this case, somehow, \input is treated in a
> very special way, and "\input filename" is different from "\input
> {filename}". I must confess to not knowing the details of how this is
> achieved, but pdfsync certainly treats them as different entities. If
> you try two files identical except that one uses \input filename and
> the other uses \input{filename}, you'll see the resulting pdfsync
> files being slightly different.
>
Sorry, you're right, only a single character or command is taken as
argument (has been a while since I looked at plain TeX). And TeX is
extremely inconsistent in this very special case. Probably because
\input is a primitive TeX command it's treated different from normal
commands, so it may be baked into TeX itself (I don't think it's part
of plain.tex).
Anyway, may main points stay: this is not a Skim issue, but a question
about latex and pdfsync. And you should not use the TeX \input command
(that's certainly how I understood his use, and to which I referred to
as not using, as I did not even realize there was another \input
command).
Christiaan
>> Christiaan
>>
>>>
>>> But pdfsync will follow \input{filename}, as a simple example can
>>> show.
>>>
>>> So if the OP is using \input{filename}, it should work.
>>>
>>> Haris Skiadas
>>> Department of Mathematics and Computer Science
>>> Hanover College
>>
>
> Haris Skiadas
> Department of Mathematics and Computer Science
> Hanover College
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Skim-app-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/skim-app-users
