File: TODO

package info (click to toggle)
octave 2.0.16-2
  • links: PTS
  • area: main
  • in suites: potato
  • size: 26,276 kB
  • ctags: 16,450
  • sloc: cpp: 67,548; fortran: 41,514; ansic: 26,682; sh: 7,361; makefile: 4,077; lex: 2,008; yacc: 1,849; lisp: 1,702; perl: 1,676; exp: 123
file content (25 lines) | stat: -rw-r--r-- 981 bytes parent folder | download | duplicates (11)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
* Write a function octave-debug which just provides the debugging
features in a restricted keymap (i.e., <prefix> l, b, f, ..., q).

* Make (un)commenting work with indented comments.  Perhaps one can simply
provide an extended comment prefix which includes leading spaces?

* Maybe also work with strings generated by single apostrophs.  (NOT for
font locking, though.)  This would require cranking up a specialized
version of octave-in-string-p.

* Bug fixes.

** Filling.

The whole code related to filling needs to be redone.  For example,

	[a b c d e] = sscanf ("This %s is %s another %s %s string", s, "C")

followed by RET will comment the "C" if auto-filling is on because the
standard function indent-new-comment-line things that it is within a
comment (because of the comment start syntax class of `%' for MATLAB
compatibility).

As long as single apostroph strings are not supported, one could simply
remove all MATLAB compatibility and change the syntax class of `%'.