Skip to content

Latest commit

 

History

History
110 lines (107 loc) · 4.1 KB

TODO.org

File metadata and controls

110 lines (107 loc) · 4.1 KB
Raw

Account for characters AFTER last respace position when respacing to a fill column

  • State “DONE” from “TODO” [2016-08-24 Wed 16:24]
  • State “TODO” from [2016-08-22 Mon 15:50]

Handle forced grouping of grouped multi-line targets as with keywords in lisp

  • State “DONE” from “TODO” [2016-08-26 Fri 23:55]
  • State “TODO” from [2016-08-22 Mon 15:51]
(multi-line-forward-sexp-find-strategy
 :split-regex "[[:space:]\n]+"
 :done-regex "[[:space:]]*)}]"
 :split-advance-fn 'multi-line-lisp-advance-fn)

Cycle through different respace strategies with multiple multi-line invocations

  • State “DONE” from “TODO” [2016-08-22 Mon 17:12]
  • State “TODO” from [2016-08-22 Mon 15:52]

Handle applying multi-line strategies in derived modes

  • State “DONE” from “TODO” [2016-08-23 Tue 13:58]
  • State “TODO” from [2016-08-22 Mon 16:03]
Should multi-line-strategy just be made buffer local? Seems like that would make things much simpler

“Aggressive” fill multi-lining

  • State “TODO” from [2016-08-22 Mon 20:56]
…Where a new-line is inserted before not doing so would exceed the fill column to avoid situations like where multi-lining becomes very ineffective 
(org-projectile:update-project-to-org-filepath-fdsafd-fds "multi-line"
                                                          (imalison:join-paths "~"))

The “aggresive” version would looke like

(org-projectile:update-project-to-org-filepath-fdsafd-fds
 "multi-line" (imalison:join-paths "~"))

Recursive multi-lining

  • State “TODO” from [2016-08-22 Mon 21:02]
Ex: 
(my-function-name "a long ass string" "more stuff" (afdasfdsa afdsafdsa afdsafdsa afdsafa afdfdsa "more crap" "crap"))

To:

(my-function-name "a long ass string" "more stuff"
                  (afdasfdsa afdsafdsa afdsafdsa afdsafa afdfdsa
                             "more crap" "crap"))

Instead of:

(my-function-name "a long ass string" "more stuff"
                  (afdasfdsa afdsafdsa afdsafdsa afdsafa afdfdsa "more crap" "crap"))

Fill column does not seem to work properly

  • State “DONE” from “TODO” [2016-08-24 Wed 16:23]
  • State “TODO” from [2015-11-27 Fri 11:58]
…in situations where the next separator mark is not on the same line as the multi-lining line because it looks at the column number position at the separator (usually ,)

Fill respacer does not consider characters from things that follow the end of the respaced definition

  • State “DONE” from “TODO” [2016-08-24 Wed 16:24]
  • Note taken on [2015-11-30 Mon 20:24]

Here is an example:

func (a *Account) paramsToStateChange(newState ordert.AccountState) *db.AccountStateChange {
}
  • State “TODO” from [2015-11-23 Mon 17:59]

Being inside of quotes can mess things up in python mode

  • State “TODO” from [2015-11-23 Mon 13:03]

ruby-map literals

  • State “DONE” from “TODO” [2016-08-26 Fri 23:56]
  • State “TODO” from [2015-11-29 Sun 23:59]

Apply hooks to existing buffers to make the right strategies active

  • State “TODO” from “TODO” [2016-08-27 Sat 12:31]

Pairing on : keywords is too aggressive, what if the :keyword is actually an argument

  • State “TODO” from [2016-08-27 Sat 12:31]