unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Mauro Aranda <maurooaranda@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 36459@debbugs.gnu.org, Leo Liu <sdl.web@gmail.com>
Subject: bug#36459: 27.0.50; octave-mode ElDoc support bug
Date: Thu, 4 Jul 2019 13:15:14 -0300	[thread overview]
Message-ID: <CABczVwf-DmxrXWHSAVOWVkY0KSbJ28+9M2T+FS+FkexCD7p5BQ@mail.gmail.com> (raw)
In-Reply-To: <d41f15fb-f073-cc78-f191-a8b30aed15b6@yandex.ru>

[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]

I forgot to say that my version of GNU Octave is 4.0.0

The problem is with the regexp used in
octave-eldoc-function-signatures.  It matches the signatures of the
function, that are output with a call to the GNU Octave function
print_usage.  It also matches an old-style of outputting these function
signatures, which was:
usage:  bar = foo ()

This output was also generated by calling the GNU Octave function usage,
like this:
usage ("bar = foo ()")
But usage has been deprecated in GNU Octave, I think in major version 4.
It's still present in my version, but I don't know about latest releases
(there's a recent GNU Octave 5.1.0)

I don't know why the author chose print_usage over the GNU Octave
function help, but when print_usage fails, due to being called with a
nonexistent function in his argument, like this:
print_usage ('A')
An error message like this one is output:
error: print_usage: 'A' not found

The regexp used is wrongly matching this line and therefore
octave-eldoc-function-signatures is not returning nil, as it should in
this case.

Best regards,
Mauro.

[-- Attachment #2: Type: text/html, Size: 1322 bytes --]

  reply	other threads:[~2019-07-04 16:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-01 14:58 bug#36459: 27.0.50; octave-mode ElDoc support bug Mauro Aranda
2019-07-03 14:43 ` Dmitry Gutov
2019-07-04 16:15   ` Mauro Aranda [this message]
2019-07-06 13:02   ` Leo Liu
2019-07-08 22:28     ` Mauro Aranda
2019-07-30 14:37       ` Dmitry Gutov
2019-07-30 17:53         ` Leo Liu
2019-07-31 14:11           ` Dmitry Gutov
2019-07-31 14:43             ` Mauro Aranda
2019-08-06 16:07               ` Mauro Aranda
2019-08-08  9:54                 ` Leo Liu
2019-08-08 11:09                   ` Mauro Aranda
2019-08-08 12:39                     ` Leo Liu
2019-08-08 13:50                       ` Eli Zaretskii
2019-08-08 15:36                         ` Leo Liu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABczVwf-DmxrXWHSAVOWVkY0KSbJ28+9M2T+FS+FkexCD7p5BQ@mail.gmail.com \
    --to=maurooaranda@gmail.com \
    --cc=36459@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=sdl.web@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).