summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorthdox <thdox@free.fr>2013-05-01 16:00:28 +0200
committerthdox <thdox@free.fr>2013-05-01 16:00:28 +0200
commit81ca614ec6431cbe79bb3b09fc4e5abb8e67fa6b (patch)
tree6b958ec3141a92f8e19d2d89a54322ba74e2616a /doc
parentae69ae5c643e9cb020018bbbd41e9ca85e292922 (diff)
downloadfork-ledger-81ca614ec6431cbe79bb3b09fc4e5abb8e67fa6b.tar.gz
fork-ledger-81ca614ec6431cbe79bb3b09fc4e5abb8e67fa6b.tar.bz2
fork-ledger-81ca614ec6431cbe79bb3b09fc4e5abb8e67fa6b.zip
Add description for menu items related to Sort
Diffstat (limited to 'doc')
-rw-r--r--doc/ledger-mode.texi28
1 files changed, 14 insertions, 14 deletions
diff --git a/doc/ledger-mode.texi b/doc/ledger-mode.texi
index 66028d51..ab47120d 100644
--- a/doc/ledger-mode.texi
+++ b/doc/ledger-mode.texi
@@ -369,17 +369,17 @@ transaction operation is in the undo buffer.
As you operating on the Ledger files, they may become disorganized. For
the most part, Ledger doesn't care, but our human brains prefer a bit of
order. Sorting the transactions in a buffer into chronological order
-can help bring order to chaos. Ledger sort @kbd{C-c C-s} will sort all
-of the transactions in a region by date. Ledger-mode isn't particularly
-smart about handling dates and it simply sorts the transactions using
-the string at the beginning of the transaction. So, you should use the
-preferred ISO 8601 standard date format @samp{YYYY/MM/DD} which easily
-sorts.
-
-Note, there is a menu entry to sort the entire buffer. Special
-transactions like automated transaction, will be moved in the sorting
-process and may not function correctly afterwards. For this reason
-there is no key sequence.
+can help bring order to chaos. Either using @samp{Sort Region} menu
+entry or typing @kbd{C-c C-s} will sort all of the transactions in
+a region by date. Ledger-mode isn't particularly smart about handling
+dates and it simply sorts the transactions using the string at the
+beginning of the transaction. So, you should use the preferred ISO 8601
+standard date format @samp{YYYY/MM/DD} which easily sorts.
+
+Note, there is a menu entry @samp{Sort Buffer} to sort the entire
+buffer. Special transactions like automated transaction, will be moved
+in the sorting process and may not function correctly afterwards. For
+this reason there is no key sequence.
You can limit the allowed sort region by using embedded Ledger-mode
markup within your ledger. For example:
@@ -396,9 +396,9 @@ markup within your ledger. For example:
<<< information to not sort >>>
@end example
-You can use menu entries to insert start and end markers. These
-functions will automatically delete old markers and put new new marker
-at point.
+You can use menu entries @samp{Mark Sort Beginning} to insert start and
+@samp{Mark Sort End} to insert end markers. These functions will
+automatically delete old markers and put new new marker at point.
@node Narrowing Transactions, , Sorting Transactions, The Ledger Buffer
@section Narrowing Transactions