TODO - clarify need behind feature; add other implementation ideas
This commit is contained in:
parent
e5281ffe52
commit
2af6b1207d
7
TODO.org
7
TODO.org
|
@ -264,8 +264,11 @@ ppp.el doesn't align plist values along the same column. It's also GPL, and I'm
|
|||
|
||||
* Maybe [0%]
|
||||
** New features [0%]
|
||||
1. [ ] 'input frontends' - a way to represent s-expressions as Markdown, Org, etc, so the entire plist can be edited in that mode.
|
||||
* As a side-effect, this will permit use of Markdown, Org, etc in keyword-values - e.g. to use markup in comments or notes.
|
||||
1. [ ] Some way to use markup (Markdown, Org, etc) for certain plist values.
|
||||
Implementation ideas -
|
||||
* A list of keys whose values are to be edited in a user-specified major mode.
|
||||
* "Input frontends" - a way to represent s-expressions as Markdown, Org, etc, so the entire plist can be edited in that mode. As a side-effect, this will permit use of Markdown, Org, etc in keyword-values - e.g. to use markup in comments or notes.
|
||||
* A binding in the key-value buffer, which will insert the string at point in a buffer of a certain mode.
|
||||
2. [ ] A custom variable containing a list of tasks
|
||||
#+BEGIN_SRC
|
||||
("A Task Name"
|
||||
|
|
Reference in New Issue