GNU bug report logs -
#17912
inferior-octave-mode: Wrong type argument: number-or-marker-p, "100000000000"
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 17912 in the body.
You can then email your comments to 17912 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#17912
; Package
emacs
.
(Thu, 03 Jul 2014 15:36:04 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Damian Nadales <damian.nadales <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Thu, 03 Jul 2014 15:36:05 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hello,
Whenever I start octave-mode from emacs I got the following error message:
inferior-octave-mode: Wrong type argument: number-or-marker-p, "100000000000"
Running it for a second time makes the error disappear.
Furthermore, the following error appears randomly (to me at least)
when using the Octave buffer:
comint-send-input: Wrong type argument: number-or-marker-p, "100000000000"
The constant 100000000000 is the same I use to set the history size of
octave in my pam_environment:
OCTAVE_HISTSIZE DEFAULT=100000000000
But I don't know how is this related to the error I got.
What could be happening?
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#17912
; Package
emacs
.
(Thu, 03 Jul 2014 15:51:02 GMT)
Full text and
rfc822 format available.
Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):
I forgot to add the system info:
Emacs : GNU Emacs 24.3.1 (x86_64-pc-linux-gnu, GTK+ Version 3.10.7)
of 2014-03-07 on lamiak, modified by Debian
Package: Emacs version 24.3.1
current state:
==============
(setq
octave-blink-matching-block t
octave-block-offset 2
octave-comment-char 35
octave-continuation-offset 4
octave-continuation-string "\\"
octave-send-echo-input t
octave-send-line-auto-forward t
octave-send-show-buffer t
)
On Thu, Jul 3, 2014 at 11:53 AM, Damian Nadales
<damian.nadales <at> gmail.com> wrote:
> Hello,
>
> Whenever I start octave-mode from emacs I got the following error message:
> inferior-octave-mode: Wrong type argument: number-or-marker-p, "100000000000"
>
> Running it for a second time makes the error disappear.
>
> Furthermore, the following error appears randomly (to me at least)
> when using the Octave buffer:
> comint-send-input: Wrong type argument: number-or-marker-p, "100000000000"
>
> The constant 100000000000 is the same I use to set the history size of
> octave in my pam_environment:
> OCTAVE_HISTSIZE DEFAULT=100000000000
>
> But I don't know how is this related to the error I got.
>
> What could be happening?
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#17912
; Package
emacs
.
(Fri, 04 Jul 2014 01:37:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 17912 <at> debbugs.gnu.org (full text, mbox):
Version:24.4
>> Whenever I start octave-mode from emacs I got the following error message:
>> inferior-octave-mode: Wrong type argument: number-or-marker-p, "100000000000"
Apparently you're the only use who sets OCTAVE_HISTSIZE ;-)
I installed the patch below which should hopefully fix this problem,
Stefan
=== modified file 'lisp/ChangeLog'
--- lisp/ChangeLog 2014-07-03 23:48:24 +0000
+++ lisp/ChangeLog 2014-07-04 01:34:57 +0000
@@ -1,3 +1,8 @@
+2014-07-04 Stefan Monnier <monnier <at> iro.umontreal.ca>
+
+ * progmodes/octave.el (inferior-octave-mode):
+ Set comint-input-ring-size to a number (bug#17912).
+
2014-07-03 Juri Linkov <juri <at> jurta.org>
* desktop.el (desktop-minor-mode-table): Add `defining-kbd-macro'
=== modified file 'lisp/progmodes/octave.el'
--- lisp/progmodes/octave.el 2014-04-12 04:07:53 +0000
+++ lisp/progmodes/octave.el 2014-07-04 01:34:11 +0000
@@ -747,9 +747,10 @@
(setq-local info-lookup-mode 'octave-mode)
(setq-local eldoc-documentation-function 'octave-eldoc-function)
- (setq comint-input-ring-file-name
- (or (getenv "OCTAVE_HISTFILE") "~/.octave_hist")
- comint-input-ring-size (or (getenv "OCTAVE_HISTSIZE") 1024))
+ (setq-local comint-input-ring-file-name
+ (or (getenv "OCTAVE_HISTFILE") "~/.octave_hist"))
+ (setq-local comint-input-ring-size
+ (string-to-number (or (getenv "OCTAVE_HISTSIZE") "1024")))
(comint-read-input-ring t)
(setq-local comint-dynamic-complete-functions
inferior-octave-dynamic-complete-functions)
bug marked as fixed in version 24.4, send any further explanations to
17912 <at> debbugs.gnu.org and Damian Nadales <damian.nadales <at> gmail.com>
Request was from
Glenn Morris <rgm <at> gnu.org>
to
control <at> debbugs.gnu.org
.
(Tue, 08 Jul 2014 01:56:02 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Tue, 05 Aug 2014 11:24:03 GMT)
Full text and
rfc822 format available.
This bug report was last modified 10 years and 322 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.