[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#582957: marked as done (ocaml-mode: Misuse of next-line)



Your message dated Tue, 21 Jun 2011 18:56:14 +0200
with message-id <4E00CD2E.4070903@debian.org>
and subject line Re: Bug#582957: ocaml-mode: Misuse of next-line
has caused the Debian Bug report #582957,
regarding ocaml-mode: Misuse of next-line
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
582957: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582957
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: ocaml-mode
Version: 3.11.2-1
Severity: normal

When using the caml-mode emacs reports that

  Warning: `next-line' used from Lisp code
  That command is designed for interactive use only

It is quite annoying (the warning splits the window and prevents font
lock to get started).

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (900, 'testing'), (400, 'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.31.12 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages ocaml-mode depends on:
ii  emacs23 [emacsen]             23.1+1-5   The GNU Emacs editor (with GTK+ us

ocaml-mode recommends no packages.

Versions of packages ocaml-mode suggests:
ii  ocaml                         3.11.2-1   ML language implementation with a 

-- no debconf information



--- End Message ---
--- Begin Message ---
Le 08/06/2011 16:44, Christophe TROESTLER a écrit :
How do you get this? next-line seems to be used in next-error, but I
couldn't exhibit this warning in practice.

Sorry, one year later, I cannot reproduce it.

Closing, then.


Cheers,

--
Stéphane


--- End Message ---

Reply to: