emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: a quick way to switch orgmode notes between read-only/editing?
Date: Thu, 17 Jul 2014 15:57:09 +0200	[thread overview]
Message-ID: <87vbqww0ju.fsf@gmail.com> (raw)
In-Reply-To: CAOQHXPryizyyxX=oNO2pOnofijk8R-HhmZG_eXxHu-vvsuvG_Q@mail.gmail.com

Xebar Saram <zeltakc@gmail.com> writes:

> Thx Thorston this looks great
>
> can you recommend a way to open all orgmode notes in view mode by
> default

you could try (untested!!)

,----
| (add-hook 'org-mode-hook 'view-mode)
`----

> i guess i would then bind a key to disable view mode to start
> editing right?

That key is 'e' for editing (or 'q' for quitting), already defined in
view-mode. 

I usually open files directly from dired with 'v' instead of 'f' in
view-mode to just have a look, and then either do 'e' or 'q'. 

> On Thu, Jul 17, 2014 at 4:13 PM, Thorsten Jolitz <tjolitz@gmail.com>
> wrote:
>
>     
>     Xebar Saram <zeltakc@gmail.com> writes:
>     
>     > hi all
>     >
>     > i keep once and a while screwing up my notes with unintended
>     editing
>     > (erroneous key presses etc) and was wondering if any one knew of
>     a way
>     > to to switch orgmode notes between read-only/editing? i have
>     used such
>     > options in previous note taking apps that had that option build
>     in but
>     > i understand that since orgmode notes are just text files its a
>     bit
>     > more complicated
>     >
>     > i would love to hear any suggestions on how you guys deal with
>     > protecting notes/data that still needs to be edited (i do use
>     git ofc
>     > but i dont always know i screwed my notes :))
>     
>     
>     ,----[ C-h f view-mode RET ]
>     | view-mode is an interactive autoloaded compiled Lisp function in
>     | `view.el'.
>     |
>     | (view-mode &optional ARG)
>     |
>     | Toggle View mode, a minor mode for viewing text but not editing
>     it.
>     | With a prefix argument ARG, enable View mode if ARG is positive,
>     | and disable it otherwise. If called from Lisp, enable View mode
>     | if ARG is omitted or nil.
>     |
>     | When View mode is enabled, commands that do not change the
>     buffer
>     | contents are available as usual. Kill commands insert text in
>     | kill buffers but do not delete. Most other commands beep and
>     | tell the user that the buffer is read-only.
>     |
>     |
>     |
>     | The following additional commands are provided. Most commands
>     | take prefix arguments. Page commands default to "page size"
>     | lines which is almost a whole window, or number of lines set by
>     | z or w.
>     | Half page commands default to and set "half page size" lines
>     | which initially is half a window full. Search commands default
>     | to a repeat count of one.
>     |
>     | H, h, ? This message.
>     | Digits provide prefix arguments.
>     | - negative prefix argument.
>     | < move to the beginning of buffer.
>     | > move to the end of buffer.
>     | o scroll so that buffer end is at last line of window.
>     | SPC scroll forward "page size" lines.
>     | With prefix scroll forward prefix lines.
>     | DEL scroll backward "page size" lines.
>     | With prefix scroll backward prefix lines.
>     | z like SPC but with prefix sets "page size" to prefix.
>     | w like DEL but with prefix sets "page size" to prefix.
>     | d scroll forward "half page size" lines. With prefix, sets
>     | "half page size" to prefix lines and scrolls forward that much.
>     | u scroll backward "half page size" lines. With prefix, sets
>     | "half page size" to prefix lines and scrolls backward that much.
>     | RET, LFD scroll forward one line. With prefix scroll forward
>     prefix line(s).
>     | y scroll backward one line. With prefix scroll backward prefix
>     line(s).
>     | F revert-buffer if necessary and scroll forward.
>     | Use this to view a changing file.
>     | = prints the current line number.
>     | % goes prefix argument (default 100) percent into buffer.
>     | g goes to line given by prefix argument (default first line).
>     | . set the mark.
>     | x exchanges point and mark.
>     | @ return to mark and pops mark ring.
>     | Mark ring is pushed at start of every successful search and when
>     | jump to line occurs. The mark is set on jump to buffer start or
>     end.
>     | m save current position in character register.
>     | ' go to position saved in character register.
>     | s do forward incremental search.
>     | r do reverse incremental search.
>     | / searches forward for regular expression, starting after
>     current page.
>     | ! and @ have a special meaning at the beginning of the regexp.
>     | ! means search for a line with no match for regexp. @ means
>     start
>     | search at beginning (end for backward search) of buffer.
>     | \ searches backward for regular expression, starting before
>     current page.
>     | n searches forward for last regular expression.
>     | p searches backward for last regular expression.
>     | q quit View mode, restoring this window and buffer to previous
>     state.
>     | q is the normal way to leave view mode.
>     | e exit View mode but stay in current buffer. Use this if you
>     started
>     | viewing a buffer (file) and find out you want to edit it.
>     | This command restores the previous read-only status of the
>     buffer.
>     | E exit View mode, and make the current buffer editable
>     | even if it was not editable before entry to View mode.
>     | Q quit View mode, restoring all windows to previous state.
>     | c quit View mode and maybe switch buffers, but don't kill this
>     buffer.
>     | C quit View mode, kill current buffer and go back to other
>     buffer.
>     |
>     | The effect of c, q and C depends on how view-mode was entered.
>     If it was
>     | entered by view-file, view-file-other-window,
>     view-file-other-frame, or
>     | M-x dired-view-file (M-x view-file, M-x view-file-other-window,
>     | M-x view-file-other-frame, or the Dired mode v command),
>     | then q will try to kill the current buffer.
>     | If view-mode was entered from another buffer, by C-c v,
>     | M-x view-buffer-other-window, M-x view-buffer-other frame, M-x
>     view-file,
>     | M-x view-file-other-window, or M-x view-file-other-frame,
>     | then c, q and C will return to that buffer.
>     |
>     | Entry to view-mode runs the normal hook `view-mode-hook'.
>     |
>     | [back]
>     `----
>     
>     --
>     cheers,
>     Thorsten
>     
>     
>
>

-- 
cheers,
Thorsten

  parent reply	other threads:[~2014-07-17 13:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-17 12:40 a quick way to switch orgmode notes between read-only/editing? Xebar Saram
2014-07-17 13:13 ` Thorsten Jolitz
2014-07-17 13:22   ` Xebar Saram
2014-07-17 13:23     ` Xebar Saram
2014-07-17 13:50       ` Thorsten Jolitz
2014-07-17 13:53       ` Nick Dokos
2014-07-17 13:57     ` Thorsten Jolitz [this message]
2014-07-17 14:46 ` Jorge A. Alfaro-Murillo
2014-07-17 15:15   ` Xebar Saram
2014-07-17 23:42     ` Eric Abrahamsen
2014-07-18  7:50       ` Xebar Saram
2014-07-18  8:54         ` Thorsten Jolitz
2014-07-18 12:14           ` Xebar Saram
2014-07-18 12:35             ` Thorsten Jolitz
2014-07-18 15:31               ` Xebar Saram
2014-07-18 20:37                 ` Thorsten Jolitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vbqww0ju.fsf@gmail.com \
    --to=tjolitz@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).