From: S.P.Tseng <deftsp@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [bug]x2 #+BEGIN_EXAMPLE can not work and #+BEGIN_SRC indent error
Date: Sun, 03 Aug 2008 20:04:49 +0800 [thread overview]
Message-ID: <851w16e23i.fsf@modprobe.cn> (raw)
In-Reply-To: 87hca65kmo.fsf@gollum.intra.norang.ca
Bernt Hansen <bernt@norang.ca> writes:
> S.P.Tseng <deftsp@gmail.com> writes:
>
>> 2. Press tab at the line "Exclusive or.", indent error.
>> #+BEGIN_SRC emacs-lisp
>> (defun org-xor (a b)
>> "Exclusive or."
>> (if a (not b) b))
>> #+END_SRC
>
> Switch to the appropriate mode first with C-c ' anywhere inside the SRC
> block and then indent works fine. You switch back to org-mode with
> another C-c '
In fact I want to stop org-mode treat [[xxxx.xx][xxxx]] as link with
#+BEGIN_EXAMPLE and #+END_EXAMPLE just like ":".
>
> I don't think it's reasonable that org-mode should know all of the
> indentation requirements for all other modes.
I do not mean org-mode should know all of the indentation requirements for all
other modes. I think the code between #+BEGIN_SRC and #+END_SRC is better to
stop indent when I press Tab in them.
Then I can use follow code two indent the whole buffer.
,----
| (defun iwb ()
| "indent whole buffer"
| (interactive)
| (delete-trailing-whitespace)
| (indent-region (point-min) (point-max) nil)
| (untabify (point-min) (point-max)))
`----
For the moment, If I use the function iwb to indent the whole buffer, the indent
of the code between #+BEGIN_SRC and #+END_SRC will be destroy.
next prev parent reply other threads:[~2008-08-03 12:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 7:24 [bug]x2 #+BEGIN_EXAMPLE can not work and #+BEGIN_SRC indent error S.P.Tseng
2008-07-31 12:00 ` Bernt Hansen
2008-08-03 12:04 ` S.P.Tseng [this message]
2008-09-07 7:09 ` Carsten Dominik
[not found] ` <851vzw3zm9.fsf@modprobe.cn>
2008-09-07 12:38 ` Fwd: " S.P.Tseng
[not found] ` <C13F6320-306D-4B16-8BB1-0F16C35A2B4D@uva.nl>
[not found] ` <85abej31br.fsf@modprobe.cn>
2008-09-08 0:57 ` S.P.Tseng
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=851w16e23i.fsf@modprobe.cn \
--to=deftsp@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.