Motivation
ned should have config file parser so that users can make "their own ned" according to their taste. But for now, we don't need a VERY POWERFUL parser (and interpreter like vim). It's future task.
Description
Config File format
I have a plan to make a config parser to parse config file like following.
# this is inline comment in config file
# following is basic config format
# `+` means 1 or more
<command> <argument>+
Config file example
set syntax
set number
set tabstop 4
set expandtab
unset syntax
unset number
unset tabstop # tabstop value will turn back to default value
unset expandtab
Config file place
According to tradition, ned reads config file from $HOME/.nedrc
Motivation
ned should have config file parser so that users can make "their own ned" according to their taste. But for now, we don't need a VERY POWERFUL parser (and interpreter like vim). It's future task.
Description
Config File format
I have a plan to make a config parser to parse config file like following.
Config file example
Config file place
According to tradition, ned reads config file from
$HOME/.nedrc