Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Two alternate chapter/section names with memoir #136

Closed
alxh opened this issue Dec 29, 2015 · 2 comments
Closed

Two alternate chapter/section names with memoir #136

alxh opened this issue Dec 29, 2015 · 2 comments

Comments

@alxh
Copy link

alxh commented Dec 29, 2015

Hi all,

The memoir class supports two alternate names for chapters and sections etc., to use for the TOC and headers, like:

\chapter[toc-name][header-name]{long-name}

whereas standard LaTeX supports only one:

\chapter[toc-and-header-name]{long-name}

Would it be possible to integrate this into the LaTeX Memoir language definition file in the tmBundle? It would be very helpful if it was recognized properly, especially for quick navigation in the document.

Thanks very much in advance!

@sanssecours sanssecours self-assigned this Dec 30, 2015
sanssecours added a commit that referenced this issue Dec 30, 2015
The Memoir document class supports headings with two optional arguments
auch as:

    \chapter[toc-name][header-name]{long-name}

This commit adds support for these extended headings. They will now
show up in the symbol list, if you use the grammar “LaTeX Memoir”. This
change fixes issue [#136].

[#136]: #136
@sanssecours
Copy link
Member

Hi Alexandre,

thank you for the well written feature request. Commit 6bc07c0 should fix your issue. If you have any additional remarks or questions, then please just comment below.

Kind regards,
René

@alxh
Copy link
Author

alxh commented Jan 2, 2016

Hi René,
Thank you so much !
And happy new year :)
Regards,

Alexandre

On Wed, Dec 30, 2015 at 6:21 PM, René Schwaiger notifications@github.com
wrote:

Hi Alexandre,

thank you for the well written feature request. Commit 6bc07c0
6bc07c0
should fix your issue. If you have any additional remarks or questions,
then please just comment below.

Kind regards,
René


Reply to this email directly or view it on GitHub
#136 (comment)
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants