Getting errors using Acro for abbreviations and acronyms: Undefined Control Sequence in acro.sty
I've been trying to use acro
for abbreviating terms in a report. It mostly works but each compile requires intervention to complete and does something to my first page, leaves an =1 and a page break. Any help would be greatly appreciated.
documentclass[A4, 12pt]{article}
% for abbreviations and acronyms
usepackage[first-style=long]{acro}
DeclareAcronym{ma}{
short = MA ,
long = Multiple Access ,
}
DeclareAcronym{noma}{
short = NOMA ,
long = Non-Orthongonal Multiple Access ,
}
% title info
title{Beamforming for Millimeter-wave acs{noma}}
author{Cian Dowd}
date{21/01/2019}
begin{document}
pagenumbering{roman}
maketitle
% ABSTRACT
begin{abstract}
In this paperldots
end{abstract}
% TABLE OF CONTENTS
tableofcontents
% LIST OF ACRONYMS
printacronyms
% INTRODUCTION
pagenumbering{arabic}
setcounter{page}{1}
setcounter{section}{0}
section{Introduction}
ac{noma}ldots
% LITERATURE REVIEW
setcounter{section}{1}
section{Background/ Literature Review}
% Background on Current MA
subsection{Existing acf{ma}}
end{document}
This yields the following document; errors shown below it.
page break
I get these messages, ending with the errors:
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/acro/acro.sty
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/l3kernel/expl3.sty
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/l3kernel/expl3-code.tex)
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/l3kernel/l3pdfmode.def))
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/l3packages/xparse/xparse.sty
)
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/l3packages/l3keys2e/l3keys2e
.sty)
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/l3packages/xtemplate/xtempla
te.sty)
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/etoolbox/etoolbox.sty)
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/oberdiek/zref-abspage.sty
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/oberdiek/zref-base.sty
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/ltxcmds.sty)
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/infwarerr.sty)
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/kvsetkeys.sty
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/etexcmds.sty
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/ifluatex.sty)))
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/kvdefinekeys.sty)
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/pdftexcmds.sty
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/ifpdf.sty))
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/oberdiek/auxhook.sty))
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/atbegshi.sty))
Runaway argument?
{bool_if:NT l__acro_sort_bool {cs_new_protected:Npn acro_sort_prop:NN ETC.
! Forbidden control sequence found while scanning use of g@addto@macro.
<inserted text>
par
l.2965 = c_minus_one
This corresponds to line 2965 of acro.sty, though I am not sure why nor do I know how to fix this issue.
Relevant snippet of acro.sty below:
seq_sort:Nn l__acro_tmpa_seq
{
int_compare:nTF
{
acro_strcmp:nn
{ str_fold_case:n {##1} }
{ str_fold_case:n {##2} }
= c_minus_one
}
{ sort_return_same: }
{ sort_return_swapped: }
}
expl3 acronyms acro
add a comment |
I've been trying to use acro
for abbreviating terms in a report. It mostly works but each compile requires intervention to complete and does something to my first page, leaves an =1 and a page break. Any help would be greatly appreciated.
documentclass[A4, 12pt]{article}
% for abbreviations and acronyms
usepackage[first-style=long]{acro}
DeclareAcronym{ma}{
short = MA ,
long = Multiple Access ,
}
DeclareAcronym{noma}{
short = NOMA ,
long = Non-Orthongonal Multiple Access ,
}
% title info
title{Beamforming for Millimeter-wave acs{noma}}
author{Cian Dowd}
date{21/01/2019}
begin{document}
pagenumbering{roman}
maketitle
% ABSTRACT
begin{abstract}
In this paperldots
end{abstract}
% TABLE OF CONTENTS
tableofcontents
% LIST OF ACRONYMS
printacronyms
% INTRODUCTION
pagenumbering{arabic}
setcounter{page}{1}
setcounter{section}{0}
section{Introduction}
ac{noma}ldots
% LITERATURE REVIEW
setcounter{section}{1}
section{Background/ Literature Review}
% Background on Current MA
subsection{Existing acf{ma}}
end{document}
This yields the following document; errors shown below it.
page break
I get these messages, ending with the errors:
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/acro/acro.sty
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/l3kernel/expl3.sty
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/l3kernel/expl3-code.tex)
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/l3kernel/l3pdfmode.def))
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/l3packages/xparse/xparse.sty
)
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/l3packages/l3keys2e/l3keys2e
.sty)
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/l3packages/xtemplate/xtempla
te.sty)
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/etoolbox/etoolbox.sty)
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/oberdiek/zref-abspage.sty
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/oberdiek/zref-base.sty
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/ltxcmds.sty)
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/infwarerr.sty)
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/kvsetkeys.sty
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/etexcmds.sty
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/ifluatex.sty)))
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/kvdefinekeys.sty)
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/pdftexcmds.sty
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/ifpdf.sty))
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/oberdiek/auxhook.sty))
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/atbegshi.sty))
Runaway argument?
{bool_if:NT l__acro_sort_bool {cs_new_protected:Npn acro_sort_prop:NN ETC.
! Forbidden control sequence found while scanning use of g@addto@macro.
<inserted text>
par
l.2965 = c_minus_one
This corresponds to line 2965 of acro.sty, though I am not sure why nor do I know how to fix this issue.
Relevant snippet of acro.sty below:
seq_sort:Nn l__acro_tmpa_seq
{
int_compare:nTF
{
acro_strcmp:nn
{ str_fold_case:n {##1} }
{ str_fold_case:n {##2} }
= c_minus_one
}
{ sort_return_same: }
{ sort_return_swapped: }
}
expl3 acronyms acro
1
See bitbucket.org/cgnieder/acro/issues/116/…
– moewe
Jan 14 at 21:20
@moewe Am I right in saying that recommends changing the contents of the file to a -1? Makes me a bit uncomfortable but I'll give it a go. Thanks!
– BitFlow
Jan 14 at 21:23
Directly editingacro.sty
would be a last resort, but I can't find a more elegant work-around at the moment sincec_minus_one
is used in anAtBeginDocument
hook, that does not quite lend itself to patching.
– moewe
Jan 14 at 21:30
@moewe I did that and it worked perfectly. Not ideal, as you said, but much appreciated. Thanks a lot. Care to write that as an answer?
– BitFlow
Jan 14 at 21:31
add a comment |
I've been trying to use acro
for abbreviating terms in a report. It mostly works but each compile requires intervention to complete and does something to my first page, leaves an =1 and a page break. Any help would be greatly appreciated.
documentclass[A4, 12pt]{article}
% for abbreviations and acronyms
usepackage[first-style=long]{acro}
DeclareAcronym{ma}{
short = MA ,
long = Multiple Access ,
}
DeclareAcronym{noma}{
short = NOMA ,
long = Non-Orthongonal Multiple Access ,
}
% title info
title{Beamforming for Millimeter-wave acs{noma}}
author{Cian Dowd}
date{21/01/2019}
begin{document}
pagenumbering{roman}
maketitle
% ABSTRACT
begin{abstract}
In this paperldots
end{abstract}
% TABLE OF CONTENTS
tableofcontents
% LIST OF ACRONYMS
printacronyms
% INTRODUCTION
pagenumbering{arabic}
setcounter{page}{1}
setcounter{section}{0}
section{Introduction}
ac{noma}ldots
% LITERATURE REVIEW
setcounter{section}{1}
section{Background/ Literature Review}
% Background on Current MA
subsection{Existing acf{ma}}
end{document}
This yields the following document; errors shown below it.
page break
I get these messages, ending with the errors:
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/acro/acro.sty
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/l3kernel/expl3.sty
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/l3kernel/expl3-code.tex)
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/l3kernel/l3pdfmode.def))
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/l3packages/xparse/xparse.sty
)
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/l3packages/l3keys2e/l3keys2e
.sty)
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/l3packages/xtemplate/xtempla
te.sty)
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/etoolbox/etoolbox.sty)
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/oberdiek/zref-abspage.sty
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/oberdiek/zref-base.sty
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/ltxcmds.sty)
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/infwarerr.sty)
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/kvsetkeys.sty
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/etexcmds.sty
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/ifluatex.sty)))
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/kvdefinekeys.sty)
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/pdftexcmds.sty
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/ifpdf.sty))
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/oberdiek/auxhook.sty))
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/atbegshi.sty))
Runaway argument?
{bool_if:NT l__acro_sort_bool {cs_new_protected:Npn acro_sort_prop:NN ETC.
! Forbidden control sequence found while scanning use of g@addto@macro.
<inserted text>
par
l.2965 = c_minus_one
This corresponds to line 2965 of acro.sty, though I am not sure why nor do I know how to fix this issue.
Relevant snippet of acro.sty below:
seq_sort:Nn l__acro_tmpa_seq
{
int_compare:nTF
{
acro_strcmp:nn
{ str_fold_case:n {##1} }
{ str_fold_case:n {##2} }
= c_minus_one
}
{ sort_return_same: }
{ sort_return_swapped: }
}
expl3 acronyms acro
I've been trying to use acro
for abbreviating terms in a report. It mostly works but each compile requires intervention to complete and does something to my first page, leaves an =1 and a page break. Any help would be greatly appreciated.
documentclass[A4, 12pt]{article}
% for abbreviations and acronyms
usepackage[first-style=long]{acro}
DeclareAcronym{ma}{
short = MA ,
long = Multiple Access ,
}
DeclareAcronym{noma}{
short = NOMA ,
long = Non-Orthongonal Multiple Access ,
}
% title info
title{Beamforming for Millimeter-wave acs{noma}}
author{Cian Dowd}
date{21/01/2019}
begin{document}
pagenumbering{roman}
maketitle
% ABSTRACT
begin{abstract}
In this paperldots
end{abstract}
% TABLE OF CONTENTS
tableofcontents
% LIST OF ACRONYMS
printacronyms
% INTRODUCTION
pagenumbering{arabic}
setcounter{page}{1}
setcounter{section}{0}
section{Introduction}
ac{noma}ldots
% LITERATURE REVIEW
setcounter{section}{1}
section{Background/ Literature Review}
% Background on Current MA
subsection{Existing acf{ma}}
end{document}
This yields the following document; errors shown below it.
page break
I get these messages, ending with the errors:
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/acro/acro.sty
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/l3kernel/expl3.sty
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/l3kernel/expl3-code.tex)
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/l3kernel/l3pdfmode.def))
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/l3packages/xparse/xparse.sty
)
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/l3packages/l3keys2e/l3keys2e
.sty)
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/l3packages/xtemplate/xtempla
te.sty)
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/etoolbox/etoolbox.sty)
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/oberdiek/zref-abspage.sty
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/oberdiek/zref-base.sty
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/ltxcmds.sty)
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/infwarerr.sty)
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/kvsetkeys.sty
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/etexcmds.sty
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/ifluatex.sty)))
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/kvdefinekeys.sty)
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/pdftexcmds.sty
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/ifpdf.sty))
(/usr/local/texlive/2016basic/texmf-dist/tex/latex/oberdiek/auxhook.sty))
(/usr/local/texlive/2016basic/texmf-dist/tex/generic/oberdiek/atbegshi.sty))
Runaway argument?
{bool_if:NT l__acro_sort_bool {cs_new_protected:Npn acro_sort_prop:NN ETC.
! Forbidden control sequence found while scanning use of g@addto@macro.
<inserted text>
par
l.2965 = c_minus_one
This corresponds to line 2965 of acro.sty, though I am not sure why nor do I know how to fix this issue.
Relevant snippet of acro.sty below:
seq_sort:Nn l__acro_tmpa_seq
{
int_compare:nTF
{
acro_strcmp:nn
{ str_fold_case:n {##1} }
{ str_fold_case:n {##2} }
= c_minus_one
}
{ sort_return_same: }
{ sort_return_swapped: }
}
expl3 acronyms acro
expl3 acronyms acro
edited Jan 14 at 21:32
moewe
88.5k9110338
88.5k9110338
asked Jan 14 at 21:19
BitFlowBitFlow
204
204
1
See bitbucket.org/cgnieder/acro/issues/116/…
– moewe
Jan 14 at 21:20
@moewe Am I right in saying that recommends changing the contents of the file to a -1? Makes me a bit uncomfortable but I'll give it a go. Thanks!
– BitFlow
Jan 14 at 21:23
Directly editingacro.sty
would be a last resort, but I can't find a more elegant work-around at the moment sincec_minus_one
is used in anAtBeginDocument
hook, that does not quite lend itself to patching.
– moewe
Jan 14 at 21:30
@moewe I did that and it worked perfectly. Not ideal, as you said, but much appreciated. Thanks a lot. Care to write that as an answer?
– BitFlow
Jan 14 at 21:31
add a comment |
1
See bitbucket.org/cgnieder/acro/issues/116/…
– moewe
Jan 14 at 21:20
@moewe Am I right in saying that recommends changing the contents of the file to a -1? Makes me a bit uncomfortable but I'll give it a go. Thanks!
– BitFlow
Jan 14 at 21:23
Directly editingacro.sty
would be a last resort, but I can't find a more elegant work-around at the moment sincec_minus_one
is used in anAtBeginDocument
hook, that does not quite lend itself to patching.
– moewe
Jan 14 at 21:30
@moewe I did that and it worked perfectly. Not ideal, as you said, but much appreciated. Thanks a lot. Care to write that as an answer?
– BitFlow
Jan 14 at 21:31
1
1
See bitbucket.org/cgnieder/acro/issues/116/…
– moewe
Jan 14 at 21:20
See bitbucket.org/cgnieder/acro/issues/116/…
– moewe
Jan 14 at 21:20
@moewe Am I right in saying that recommends changing the contents of the file to a -1? Makes me a bit uncomfortable but I'll give it a go. Thanks!
– BitFlow
Jan 14 at 21:23
@moewe Am I right in saying that recommends changing the contents of the file to a -1? Makes me a bit uncomfortable but I'll give it a go. Thanks!
– BitFlow
Jan 14 at 21:23
Directly editing
acro.sty
would be a last resort, but I can't find a more elegant work-around at the moment since c_minus_one
is used in an AtBeginDocument
hook, that does not quite lend itself to patching.– moewe
Jan 14 at 21:30
Directly editing
acro.sty
would be a last resort, but I can't find a more elegant work-around at the moment since c_minus_one
is used in an AtBeginDocument
hook, that does not quite lend itself to patching.– moewe
Jan 14 at 21:30
@moewe I did that and it worked perfectly. Not ideal, as you said, but much appreciated. Thanks a lot. Care to write that as an answer?
– BitFlow
Jan 14 at 21:31
@moewe I did that and it worked perfectly. Not ideal, as you said, but much appreciated. Thanks a lot. Care to write that as an answer?
– BitFlow
Jan 14 at 21:31
add a comment |
1 Answer
1
active
oldest
votes
The constant c_minus_one
was removed from LaTeX3 in the end-of-year deprecation round for 2018. acro.sty
is still using it, though, and that causes issues with new versions of the LaTeX3 kernel. See https://bitbucket.org/cgnieder/acro/issues/116/acro-errors-due-to-update-c_minus_one.
You could manually edit acro.sty
and change the c_minus_one
to -1
. Keep in mind, however, that usually edits like this to distributed files are strongly discouraged. In this case the edit could be justified because the file is unusable without it and an updated version of acro.sty
that would make the fix unnecessary would overwrite your fixed version.
You could also reinstate the command (cf. https://github.com/latex3/latex3/commit/c96faed90a5a63ba84695190560bdacac1dfdacc#diff-645783629830bdaaeede08f6ea12cb15)
usepackage{expl3}
makeatletter
ExplSyntaxOn
cs_gset_eq:NN c_deprecateacro_minus_one m@ne
tex_let:D c_minus_one c_deprecateacro_minus_one
ExplSyntaxOff
makeatother
% for abbreviations and acronyms
usepackage[first-style=long]{acro}
I guess the LaTeX3 team don't really want to see that either, so until acro
gets fixed by the maintainer you are stuck with several bad options.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f470145%2fgetting-errors-using-acro-for-abbreviations-and-acronyms-undefined-control-sequ%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The constant c_minus_one
was removed from LaTeX3 in the end-of-year deprecation round for 2018. acro.sty
is still using it, though, and that causes issues with new versions of the LaTeX3 kernel. See https://bitbucket.org/cgnieder/acro/issues/116/acro-errors-due-to-update-c_minus_one.
You could manually edit acro.sty
and change the c_minus_one
to -1
. Keep in mind, however, that usually edits like this to distributed files are strongly discouraged. In this case the edit could be justified because the file is unusable without it and an updated version of acro.sty
that would make the fix unnecessary would overwrite your fixed version.
You could also reinstate the command (cf. https://github.com/latex3/latex3/commit/c96faed90a5a63ba84695190560bdacac1dfdacc#diff-645783629830bdaaeede08f6ea12cb15)
usepackage{expl3}
makeatletter
ExplSyntaxOn
cs_gset_eq:NN c_deprecateacro_minus_one m@ne
tex_let:D c_minus_one c_deprecateacro_minus_one
ExplSyntaxOff
makeatother
% for abbreviations and acronyms
usepackage[first-style=long]{acro}
I guess the LaTeX3 team don't really want to see that either, so until acro
gets fixed by the maintainer you are stuck with several bad options.
add a comment |
The constant c_minus_one
was removed from LaTeX3 in the end-of-year deprecation round for 2018. acro.sty
is still using it, though, and that causes issues with new versions of the LaTeX3 kernel. See https://bitbucket.org/cgnieder/acro/issues/116/acro-errors-due-to-update-c_minus_one.
You could manually edit acro.sty
and change the c_minus_one
to -1
. Keep in mind, however, that usually edits like this to distributed files are strongly discouraged. In this case the edit could be justified because the file is unusable without it and an updated version of acro.sty
that would make the fix unnecessary would overwrite your fixed version.
You could also reinstate the command (cf. https://github.com/latex3/latex3/commit/c96faed90a5a63ba84695190560bdacac1dfdacc#diff-645783629830bdaaeede08f6ea12cb15)
usepackage{expl3}
makeatletter
ExplSyntaxOn
cs_gset_eq:NN c_deprecateacro_minus_one m@ne
tex_let:D c_minus_one c_deprecateacro_minus_one
ExplSyntaxOff
makeatother
% for abbreviations and acronyms
usepackage[first-style=long]{acro}
I guess the LaTeX3 team don't really want to see that either, so until acro
gets fixed by the maintainer you are stuck with several bad options.
add a comment |
The constant c_minus_one
was removed from LaTeX3 in the end-of-year deprecation round for 2018. acro.sty
is still using it, though, and that causes issues with new versions of the LaTeX3 kernel. See https://bitbucket.org/cgnieder/acro/issues/116/acro-errors-due-to-update-c_minus_one.
You could manually edit acro.sty
and change the c_minus_one
to -1
. Keep in mind, however, that usually edits like this to distributed files are strongly discouraged. In this case the edit could be justified because the file is unusable without it and an updated version of acro.sty
that would make the fix unnecessary would overwrite your fixed version.
You could also reinstate the command (cf. https://github.com/latex3/latex3/commit/c96faed90a5a63ba84695190560bdacac1dfdacc#diff-645783629830bdaaeede08f6ea12cb15)
usepackage{expl3}
makeatletter
ExplSyntaxOn
cs_gset_eq:NN c_deprecateacro_minus_one m@ne
tex_let:D c_minus_one c_deprecateacro_minus_one
ExplSyntaxOff
makeatother
% for abbreviations and acronyms
usepackage[first-style=long]{acro}
I guess the LaTeX3 team don't really want to see that either, so until acro
gets fixed by the maintainer you are stuck with several bad options.
The constant c_minus_one
was removed from LaTeX3 in the end-of-year deprecation round for 2018. acro.sty
is still using it, though, and that causes issues with new versions of the LaTeX3 kernel. See https://bitbucket.org/cgnieder/acro/issues/116/acro-errors-due-to-update-c_minus_one.
You could manually edit acro.sty
and change the c_minus_one
to -1
. Keep in mind, however, that usually edits like this to distributed files are strongly discouraged. In this case the edit could be justified because the file is unusable without it and an updated version of acro.sty
that would make the fix unnecessary would overwrite your fixed version.
You could also reinstate the command (cf. https://github.com/latex3/latex3/commit/c96faed90a5a63ba84695190560bdacac1dfdacc#diff-645783629830bdaaeede08f6ea12cb15)
usepackage{expl3}
makeatletter
ExplSyntaxOn
cs_gset_eq:NN c_deprecateacro_minus_one m@ne
tex_let:D c_minus_one c_deprecateacro_minus_one
ExplSyntaxOff
makeatother
% for abbreviations and acronyms
usepackage[first-style=long]{acro}
I guess the LaTeX3 team don't really want to see that either, so until acro
gets fixed by the maintainer you are stuck with several bad options.
answered Jan 14 at 21:40
moewemoewe
88.5k9110338
88.5k9110338
add a comment |
add a comment |
Thanks for contributing an answer to TeX - LaTeX Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f470145%2fgetting-errors-using-acro-for-abbreviations-and-acronyms-undefined-control-sequ%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
See bitbucket.org/cgnieder/acro/issues/116/…
– moewe
Jan 14 at 21:20
@moewe Am I right in saying that recommends changing the contents of the file to a -1? Makes me a bit uncomfortable but I'll give it a go. Thanks!
– BitFlow
Jan 14 at 21:23
Directly editing
acro.sty
would be a last resort, but I can't find a more elegant work-around at the moment sincec_minus_one
is used in anAtBeginDocument
hook, that does not quite lend itself to patching.– moewe
Jan 14 at 21:30
@moewe I did that and it worked perfectly. Not ideal, as you said, but much appreciated. Thanks a lot. Care to write that as an answer?
– BitFlow
Jan 14 at 21:31