#2 User definable commands to parser


The user should have the option to insert a couple of
commands, that will be interpreted as a specific item
by the internal document parser (i.e. a list of
commands, which will be equivalent to the \chapter-
command, etc.).

This should be flexible enough, to support labels and
further information, like a short version for headers
(the optional argument of the sectioning command) and
captions for objects like figures, etc.). The
description, how to recognize all those fields should
be done by regular expressions.

There should be the possibility to group some of those
definitions and import and export them (via XML), so
that the users can create descriptions for LaTeX
packages and exchange thos description-packages.


  • Sven Wiegand

    Sven Wiegand - 2002-03-18
    • milestone: 190532 --> Final_Release_(1.0)
    • summary: Userdefinable commands to parser --> User definable commands to parser
  • Tino Weinkauf

    Tino Weinkauf - 2002-04-23

    Logged In: YES

    I will need some time for this, but have some nice ideas.

  • Tino Weinkauf

    Tino Weinkauf - 2002-04-23
    • assigned_to: nobody --> niteria
  • Tino Weinkauf

    Tino Weinkauf - 2002-08-19

    Logged In: YES

    Regarding this, a user wrote:

    Currently, the parser which
    produces the structure view
    appears to only search under the
    directory of the main
    tex file in a project, for its files. Often included tex,

    bibtex and grahics files are not under this directory. Can
    parser be extended to search other directories:

    e.g. see if the \graphicspath directive is specified in the
    tex file and search under this.

    BiBTeX and TeX Files
    under the local TeXMF path specified in the

    Alternatively, these could be given as extra
    options; e.g. the ability to specify include directories for

    tex, bibtex and graphics, for the parser, that would be

    I think, the parser should never look into the
    MikTeX config, but to specify some directories would be okay. But I
    doubt, that this is really usefull to most of the

    \graphicspath is needed anyway.

  • Anonymous - 2002-09-09

    Logged In: YES

    One user just suggested the following:

    Let change/choose the tag used to identify the image
    files in a tex document. To use both pdftex and tex I use
    a command of mine, so the images are not listed.

  • Tino Weinkauf

    Tino Weinkauf - 2003-04-24
    • assigned_to: niteria --> nobody
  • Tino Weinkauf

    Tino Weinkauf - 2003-04-24

    Logged In: YES

    I am unassigning myself due to time problems. But if someone
    is going to implement this, he/she can always ask me if some
    problems occur.

  • Sven Wiegand

    Sven Wiegand - 2003-07-15
    • assigned_to: nobody --> svenwiegand
  • Sven Wiegand

    Sven Wiegand - 2003-12-14
    • assigned_to: svenwiegand --> nobody
  • Tino Weinkauf

    Tino Weinkauf - 2010-03-07

    One of our users suggested this approach:

    I'm currently using texniccenter to write presentations using beamer. I have the need to locate the frames quickly. I'm using the Navigator, Objects, Other Environments, but it could be better.

    What if I could define something like:



    - "Frames" is the name to apear in the Navigator
    - "frametitle{(.*)}" is the regular expression to be located, including the string to be removed to include in the index.

    So, having frametitle{Myframe} could apead in the navigator as:
    - Frames
    - My Frame

    This could be in an external config file so other patterns could be added. We could add indexes for anything.

    That's it
    I would love this feature

  • Tino Weinkauf

    Tino Weinkauf - 2010-03-07
    • priority: 7 --> 8


Cancel  Add attachments

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks