By the way, I meant to put
\paragraph
\subparagraph
in the list in the previous message (I think someone else mentioned
these). Additionally, it's common to see people (or special document
classes) define crazy things like
\subsubsubsubsection
... It's probably not critical that you worry about those.
ADDITIONALLY, Vim-LaTeX created commented sections for structure... like
%fakesection{...}
It's not critical that you notice these, but it's common to see these
when Vimmers people use Vim-LaTeX.
>> \section[optional shortname]{Long name}
>> \subsection*{Unnumbered section}
>
> What about the * in the first example, where can it be?
> \section[optional shortname]{Long name}
That example is valid.
> \section*[optional shortname]{Long name}
> \section[optional shortname]*{Long name}
Both of these examples are invalid for \section.
For \section, ...
\section{Title} :
Creates a NUMBERED section called "Title". Because the section is
numbered, it will show up in the table of contents, and its title will
be "Title".
\section[Short Title]{Very Long Title}
Creates a NUMBERED section called "Very Long Title". It will show up in
the table of contents under "Short Title."
\section*{Some Title}
Creates an UNNUMBERED section called "Some Title." Because it's
unnumbered, it won't show up in the table of contents, and so it can't
take an optional argument.
So the * denotes an unnumbered section (i.e., a heading without a counter).
> Assuming there are short names, which name should the tag show?
> Sounds like the short name as it will be more readily readable?
That's a reasonable point. I'd say to use the short name if provided. If
not provided (of course), use the long name.
> Is this really necessary for navigation?
> Won't there only be 1 of these tags?
There can be some code before the \documentclass. Additionally, there
are often comments before the document class.
Vim-LaTeX will fold the documentclass together.
Additionally, the section between \documentclass and \begin{document} is
the preamble, and that preamble won't have any sections. The preamble
itself is a noteworthy section. That's why it might be nice to keep
those in mind.
> I always need specifics.
> If macros can be user defined, I am not sure how the parser is
> supposed to know this isn't just another item the parser isn't looking
> for.
I wouldn't worry about user-defined macros. Is it possible to make
things user extensible though?
--Ted (who has never used ctags in Vim)
--
Ted Pavlic <[email protected]>
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
