Mercurial > octave-nkf
view .hgignore @ 20510:7fa1970a655d
pkg.m: drop check of nargout value, the interpreter already does that.
* scripts/pkg/pkg.m: the interpreter already checks if there was any variable
that got no value assigned, there's no need to make the code more
complicated to cover that. Also, there's no point in calling describe()
with different nargout since it doesn't check nargout.
author | Carnë Draug <carandraug@octave.org> |
---|---|
date | Thu, 03 Sep 2015 16:21:08 +0100 |
parents | c16c446204e5 |
children |
line wrap: on
line source
syntax: regexp # The recurrent (^|/) idiom in the regexps below should be understood # to mean "at any directory" while the ^ idiom means "from the # project's top-level directory". # gnulib makes these silly backup files .~$ # This directory gets created by gnulib during the build. # It contains no Octave files. ^libgnu/* # This directory mostly contains cruft during build time, but it does # contain some Octave code, so we gotta be a bit more careful about # what we ignore here ^m4/(?!ax_).+\.m4$ # Emacs tools create these (^|/)TAGS$ (^|/)semantic.cache$ (/|^)Makefile\.in$ ^INSTALL$ ^aclocal\.m4$ ^build-.*($|/) ^configure$ ^autom4te\.cache($|/) ^config\.in\.h$ # e.g. doc/faq/OctaveFAQ.info # doc/interpreter/octave.info-4 ^doc/.*\.info(-\d)?$ ^doc/\w*/stamp-(vti|\d+)$ ^doc/\w*/version-\w+\.texi$ ^doc/interpreter/images\.mk$ # e.g. liboctave/operators/smx-op-inc.mk ^liboctave/operators/\w+-op-\w+\.mk$ ^libinterp/dldfcn/module\.mk$