From: Glenn Morris <rgm@gnu.org>
To: "Francesco Potortì" <pot@gnu.org>
Cc: stephen@gnu.org, Kurt.Hornik@wu-wien.ac.at,
21162@debbugs.gnu.org, "John W. Eaton" <jwe@degreesofgray.org>,
Mike Miller <mtmiller@octave.org>
Subject: bug#21162: adapting octave-inf.el to Octave 4
Date: Fri, 31 Jul 2015 11:39:10 -0400 [thread overview]
Message-ID: <n0twsk49r5.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <E1ZL6Zl-0002nR-TE@tucano.isti.cnr.it> ("Francesco \=\?utf-8\?Q\?Potort\=C3\=AC\=22's\?\= message of "Fri, 31 Jul 2015 11:26:01 +0200")
Francesco Potortì wrote:
> --no-line-editing serves no apparent purpose (any more?) and prevents an
> inferior Octave process from using readline features, like getting the
> terminal width and other functions used for the FLTK graphical backend.
vc-annotate is your friend, and shows that this was added in:
commit 48495f0fd6afc6aa45f87116552629df39268336
Author: Stephen Eglen <stephen@gnu.org>
Date: Mon Sep 6 19:20:29 1999 +0000
add --no-line-editing to inferior-octave-startup-args so that TABs
in source files are not interpreted as completion requests.
I don't use Octave myself, so I have no idea if this is still relevant.
If you know it isn't, I suggest you feel free to commit this.
Please bump the defcustom's :version tag (to 25.1) if you do,
and then close this bug. Thanks!
next prev parent reply other threads:[~2015-07-31 15:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 17:22 bug#21162: adapting octave-inf.el to Octave 4 Francesco Potortì
2015-07-31 6:47 ` Glenn Morris
2015-07-31 9:26 ` Francesco Potortì
2015-07-31 15:39 ` Glenn Morris [this message]
2015-08-06 13:15 ` Francesco Potortì
2021-05-26 22:58 ` bug#21150: 24.5; octave-inf mode does not need --no-line-editing Lars Ingebrigtsen
2021-06-08 13:09 ` bug#21162: " Francesco Potortì
2021-06-09 9:35 ` Lars Ingebrigtsen
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=n0twsk49r5.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=21162@debbugs.gnu.org \
--cc=Kurt.Hornik@wu-wien.ac.at \
--cc=jwe@degreesofgray.org \
--cc=mtmiller@octave.org \
--cc=pot@gnu.org \
--cc=stephen@gnu.org \
/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).