[Octave-bug-tracker] [bug #48722] Unescape quotes in @qcode macro to avoid a Texinfo parsing error

[Rafael Laboissiere]

Follow-up Comment #2, bug #48722 (project octave):

Hi Anonymous,

Thanks for your comments.  Actually, the construct @qcode{\"something\"}
appears only in two files:


$ find . -name "*.m" -exec grep -l '@qcode{\\"' {} \;
./scripts/deprecated/luinc.m
./doc/interpreter/genpropdoc.m


For the first case, besides the fact the script luinc.m is deprecated,
@qcode{\"vector\"} should read, in fact, @qcode{"vector"}.  Otherwise, the
documentation looks awkward.

For the second case (genpropdoc.m), all occurrences of the construct
@qcode{\"something\"} appear inside strings in the Octave code.  That is the
reason the double quotes must be escaped.

However, the above does not answer your question.  The bug in the docstring
for qrdelete is triggered because that docstring is processed by texinfo, in
the process of building the Octave manual, which is not the case for luinc. 
Indeed, you can try:


info octave --index-search=qrdelete
info octave --index-search=luinc


Rafael Laboissière

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?48722>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/