emacs-elpa-diffs
[Top][All Lists]
Advanced

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

[elpa] master 625353b 427/433: (Mostly) remove some earlier entries


From: Dmitry Gutov
Subject: [elpa] master 625353b 427/433: (Mostly) remove some earlier entries
Date: Thu, 15 Mar 2018 19:44:48 -0400 (EDT)

branch: master
commit 625353b412ee3f14d09a566beb8e90a990b19443
Author: Dmitry Gutov <address@hidden>
Commit: Dmitry Gutov <address@hidden>

    (Mostly) remove some earlier entries
---
 TODO | 15 ++-------------
 1 file changed, 2 insertions(+), 13 deletions(-)

diff --git a/TODO b/TODO
index 718e049..c31c0d3 100644
--- a/TODO
+++ b/TODO
@@ -3,10 +3,6 @@ Hey Emacs, this is a -*-text-*- file!
                        To Do List for MMM Mode
                        =======================
 
-It would be nice to have a "split region" command which would insert
-a _back_ delimiter followed by a _front_ delimiter at point and split
-the current region into two regions.  Say for PHP.
-
 Custom mode functions like `mason-mode'.
 
 Make Mason work a little better with PSGML.  The fix I've found works,
@@ -30,14 +26,6 @@ syntax properties.
 
 Trap paragraph motion commands to stop at submode boundaries?
 
-On text insertion (in `after-change-functions'), do two things.
-First, if inside in a region, or after a hanging one, scan for its
-back and adjust if necessary.  Second, scan both for complete regions
-and for hanging fronts.  In the latter case, we may insert the back or
-start a hanging region; user option.  Don't just scan the inserted
-text, but backwards, using `mmm-looking-back-at'.  Remember to handle
-delimiter inclusion and offsets as best possible.
-
 It would be nice if C-j ended a Mason one-liner and began a new one on
 the next line.  This is a rather Mason-specific thing, but other
 classes might have similar single-line regions.  Add a new submode
@@ -66,4 +54,5 @@ of the most early change, see the submodes nesting there, and 
resume
 parsing with that data. Shouldn't be too hard, conceptually. Maybe
 even ignore the nesting, backtrack to a position where there are no
 overlays, and re-parse from there (see mmm-parse-apply as a starting
-point).
+point). Remember to handle delimiter inclusion and offsets as best
+possible.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]