emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bastien.guerry@wikimedia.fr>
To: Anders Waldenborg <anders@0x63.nu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Deriving mode from org-mode
Date: Tue, 15 Feb 2011 05:11:18 +0100	[thread overview]
Message-ID: <877hd2q6mx.fsf@gnu.org> (raw)
In-Reply-To: <4D584BE5.2050401@0x63.nu> (Anders Waldenborg's message of "Sun, 13 Feb 2011 22:23:49 +0100")

Hi Anders,

Anders Waldenborg <anders@0x63.nu> writes:

> isn't creating a new major mode derived from org-mode supported?

Yes it is...

> I guess that part of the problem is that org-mode-p doesn't use 
> derived-mode-p.

(org-mode-p) does the advertized job: checking whether we are in
org-mode major mode.  It would be confusing to also check against 
org derived modes, at least with that function's name.

> For example:
> (define-derived-mode org-derived-mode org-mode "Org-Derived")
>
> and then create a new buffer using org-derived-mode and enter a source 
> block, like this:
>
> #+BEGIN_SRC emacs-lisp
> #+END_SRC
>
> and do org-edit-special (C-c ') in that buffer. When finishing editing 
> one gets this message:
> "org-edit-src-exit: This is not a sub-editing buffer, something is
> wrong"

Fixed, I corrected this directly in `org-edit-src-code', allow source
code to be edited from org-mode derived modes.

Can you share what kind of derived mode you're writing?  What for?

Thanks,

-- 
 Bastien

  reply	other threads:[~2011-02-15  4:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-13 21:23 Deriving mode from org-mode Anders Waldenborg
2011-02-15  4:11 ` Bastien [this message]
2011-02-22  9:17   ` Anders Waldenborg
2011-02-22  9:21     ` Carsten Dominik
2011-02-22  9:34       ` Carsten Dominik
2011-02-22 21:31         ` Anders Waldenborg
2011-02-22 11:52     ` Bastien
2011-07-15 19:50       ` [Orgmode] " Anders Waldenborg

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=877hd2q6mx.fsf@gnu.org \
    --to=bastien.guerry@wikimedia.fr \
    --cc=anders@0x63.nu \
    --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).