1 |
On Sat, 4 Apr 2009 21:33:39 +0200 |
2 |
Christian Faulhammer <fauli@g.o> wrote: |
3 |
> > So what I'd like to be able to do is have it say "see section |
4 |
> > [funcs.src_unpack.3]" rather than "see section 1.2.3.4", and then |
5 |
> > when we have a labelled section, lay it out something like: |
6 |
> |
7 |
> What is possible is to reference the heading of the section and even |
8 |
> the name from \label. Displaying the label names in the margin should |
9 |
> be feasible, too, as far as I remember. |
10 |
|
11 |
That would be helpful. |
12 |
|
13 |
> > I realise this is somewhat getting away from your original patch. |
14 |
> > But I strongly suspect that the cheat sheet will be a lot more |
15 |
> > useful if it has references to exactly what the new src_unpack is, |
16 |
> > for when people need to look it up -- and it would help if people |
17 |
> > didn't have to print out a new cheatsheet to get valid section |
18 |
> > references every time we tweak the wording in such a way that the |
19 |
> > section numbers change... |
20 |
> |
21 |
> Correct, but a task I can't handle in the near future, I can give |
22 |
> some advise though and someone labelling all appropriate paragraphs |
23 |
> would do the biggest part. They should have a naming scheme like: |
24 |
> eapi4:<function>:<name> where function is something like |
25 |
> install|phase|etc. |
26 |
|
27 |
Yeah, that'd work. |
28 |
|
29 |
I'm wondering what our best merge strategy is here. I'm inclined to |
30 |
think we're best off fixing all the labels on the eapi-3 branch (even |
31 |
if we can't get them displayed or used for named references just yet), |
32 |
rebasing that onto master (not much has diverged) once we have the |
33 |
go-ahead from the Council either next meeting or the one after |
34 |
(probably...) and then doing the cheat-sheet with EAPI 3 included on top |
35 |
of that. |
36 |
|
37 |
Or were you particularly desperate to get the cheat-sheet in for EAPI 2? |
38 |
|
39 |
-- |
40 |
Ciaran McCreesh |