From: Andrea Valle <valle@di.unito.it>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: list of figures
Date: Fri, 14 Sep 2018 15:24:22 +0200 [thread overview]
Message-ID: <536DF684-BABB-411F-8F5C-9D1B52FAAC78@di.unito.it> (raw)
In-Reply-To: <20180914064055.3cef6b54@comcast.net>
[-- Attachment #1.1: Type: text/plain, Size: 1883 bytes --]
Thanks to all, yes, \placelistoffigures works fine
Concerning structure: yeah, thanks Alan, I used it. I think I had some issues I was not able to solve so switched to raw input.
Best
-a-
--------------------------------------------------
Andrea Valle
--------------------------------------------------
CIRMA - StudiUm
Università degli Studi di Torino
--> http://www.cirma.unito.it/andrea/
--> http://www.fonurgia.unito.it/andrea/
--> http://www.flickr.com/photos/vanderaalle/sets/
--> http://vimeo.com/vanderaalle
--> http://andreavalle.bandcamp.com
--> andrea.valle@unito.it
--------------------------------------------------
"This is a very complicated case, Maude. You know, a lotta ins, a lotta outs, a lotta what-have-yous."
(Jeffrey 'The Dude' Lebowski)
> On 14 Sep 2018, at 14:40, Alan Braslau <braslau.list@comcast.net> wrote:
>
> On Fri, 14 Sep 2018 11:20:27 +0200
> Andrea Valle <valle@di.unito.it> wrote:
>
>> Thanks Henri
>>
>> actually this works in my chapter but I have a book made up of various chapters coordinate by a main.tex file
>> containing general setting and e.g.
>>
>> \input c_1_semiotics.tex % chapter
>>
>> \input c_2_conceptions.tex
>>
>> etc
>
> The ConTeXt way of doing this is:
>
> \component c_1_semiotics
>
> \component c_2_conceptions
>
> also putting
>
> \startcomponent c_1_semiotics
> ...
> \stopcomponent
>
> at the beginning and end in each component file.
>
> This project/product scheme is handled more coherently than a raw \input. Note, however, that this has nothing to do directly with the question about generating a list of figures; as already answered \placelistoffigures[criterium=chapter], for example, gives a list of figures limited to the present chapter. One can also use criterium=part, section, etc. as well as criterium=all.
>
> Alan
>
[-- Attachment #1.2: Type: text/html, Size: 3915 bytes --]
[-- Attachment #2: Type: text/plain, Size: 492 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2018-09-14 13:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 8:50 Andrea Valle
2018-09-14 8:58 ` Henri Menke
2018-09-14 9:20 ` Andrea Valle
2018-09-14 9:35 ` cryo shock
2018-09-14 12:40 ` Alan Braslau
2018-09-14 13:24 ` Andrea Valle [this message]
[not found] <4676D805.4050405@wxs.nl>
2007-06-26 15:07 ` List " Horacio Suarez
-- strict thread matches above, loose matches on Subject: below --
2000-02-09 6:11 Dan Seracu
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=536DF684-BABB-411F-8F5C-9D1B52FAAC78@di.unito.it \
--to=valle@di.unito.it \
--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).