From: Carsten Dominik <carsten.dominik@gmail.com>
To: Dan Davison <davison@stats.ox.ac.uk>
Cc: emacs org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Saving the *Org Edit Src Example* buffer
Date: Tue, 2 Jun 2009 19:12:54 +0200 [thread overview]
Message-ID: <BF98B563-9E06-42C4-96D0-9EFBC48224E9@gmail.com> (raw)
In-Reply-To: <87prdmljpo.fsf@stats.ox.ac.uk>
Applied, thanks.
- Carsten
On Jun 2, 2009, at 5:49 PM, Dan Davison wrote:
> Dan Davison <davison@stats.ox.ac.uk> writes:
>
>> Following on from the recent improvements to the *Org Edit Src
>> Example*
>> buffer, I have one more proposal: I have remapped C-x C-s so that it
>> saves the code in the org buffer, rather than offering to save the
>> Edit
>> buffer itself (as it used to be with the indirect edit buffer). I
>> find
>> this essential, although I recognise that remapping C-x C-s is a
>> rather
>> radical thing to do to an emacs buffer.
>>
>> I am using the simple-minded approach below; it seems to work fine (I
>
> Hmm, well I had used that for at least a week before posting, but I
> have
> now noticed a problem. It's a bit of a corner case. If you create
> extra
> blank lines at the end of the source code edit buffer and leave point
> down there, then do org-edit-src-exit, now back in the org buffer
> point
> is outside the source code block. In that case, the code that I just
> posted doesn't work. I suggest that org-edit-src-exit should in this
> situation place point at the end of the source code block, for example
> like this:
>
>
> diff --git a/lisp/org.el b/lisp/org.el
> index 659dfad..be459b5 100644
> --- a/lisp/org.el
> +++ b/lisp/org.el
> @@ -6757,7 +6757,9 @@ the language, a switch telling of the content
> should be in a single line."
> code)
> (goto-char (point-min))
> (if (looking-at "[ \t\n]*\n") (replace-match ""))
> - (if (re-search-forward "\n[ \t\n]*\\'" nil t) (replace-match ""))
> + (when (re-search-forward "\n[ \t\n]*\\'" nil t)
> + (replace-match "")
> + (setq line (min line (org-current-line))))
> (when (org-bound-and-true-p org-edit-src-force-single-line)
> (goto-char (point-min))
> (while (re-search-forward "\n" nil t)
>
>
> Dan
>
>
>
>
>> don't even notice a flicker -- should I be surprised at that?), but
>> if
>> someone can suggest an improved implementation I'd be happy to
>> learn how
>> it should be done (perhaps there are buffer variables other than
>> point
>> and mark that I should restore? Is there a general mechanism I should
>> use for this?).
>>
>> Dan
>>
>> (defun org-edit-src-save ()
>> "Update the parent org buffer with the edited source code, save
>> the parent org-buffer, and return to the source code edit
>> buffer."
>> (interactive)
>> (let ((p (point))
>> (m (mark)))
>> (org-edit-src-exit)
>> (save-buffer)
>> (org-edit-src-code)
>> (set-mark m)
>> (goto-char p)))
>>
>> (define-key org-exit-edit-mode-map "\C-x\C-s" 'org-edit-src-save)
>>
>>
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Remember: use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2009-06-02 17:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 15:02 Saving the *Org Edit Src Example* buffer Dan Davison
2009-06-02 15:49 ` Dan Davison
2009-06-02 17:12 ` Carsten Dominik [this message]
2009-06-09 14:51 ` Dan Davison
2009-06-09 18:20 ` Carsten Dominik
2009-06-02 17:04 ` Carsten Dominik
2009-08-11 16:44 ` PATCH: proposed improvements to org-src-mode Dan Davison
2009-08-12 12:22 ` Carsten Dominik
2009-08-12 14:58 ` Dan Davison
2009-08-19 11:03 ` Dan Davison
2009-08-24 12:17 ` Carsten Dominik
2009-08-28 2:36 ` Dan Davison
2009-08-28 7:59 ` Carsten Dominik
2009-09-05 17:33 ` Dan Davison
2009-09-06 11:41 ` Carsten Dominik
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=BF98B563-9E06-42C4-96D0-9EFBC48224E9@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=davison@stats.ox.ac.uk \
--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).