all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Garreau\, Alexandre" <galex-713@galex-713.eu>
To: emacs-orgmode@gnu.org
Subject: Re: Fixed [
Date: Wed, 24 Oct 2018 18:45:02 +0200	[thread overview]
Message-ID: <87h8hb9tv5.fsf@portable.galex-713.eu> (raw)
In-Reply-To: <87va5rwcbl.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Wed, 24 Oct 2018 18:15:26 +0200")

Le 24/10/2018 à 18h15, Nicolas Goaziou a écrit :
> "Garreau, Alexandre" <galex-713@galex-713.eu> writes:
>> On 2018-10-24 at 17:31, Garreau, Alexandre wrote:
>>> I finally found how people naturally made their mail with org, with
>>> orgstruct++-mode, that I just tried.  However that triggers an infinite
>>> loop error (“car: Lisp nesting exceeds ‘max-lisp-eval-depth’”), because
>>> then indent-line-function refers to org-indent-line, which when
>>> orgstruct-is-++ is true, calls indent-line-function.
>>>
>>> Why that garbage? how is it supposed to be?
>>
>> Ok, then (cl-cadadr (assq 'indent-line-function org-fb-vars)) is
>> supposed *not* to return org-indent-line, as now I cleaned my hooks
>> (some modes where called several times redundantly in message-mode,
>> text-mode, etc.), I see no more problems, sorry for the disturbance.
>
> Note that orgstruct-mode, and orgstruct++-mode are removed from the code
> base.

No really? how sad! do anyone knows why?

And also what are we supposed to use to support src blocks and
outline-like headings in Gnus?

  reply	other threads:[~2018-10-24 16:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-24 15:31 org-indent-line loops infinitely (when orgstruct++) Garreau, Alexandre
2018-10-24 15:45 ` Fixed [Was: Re: org-indent-line loops infinitely (when orgstruct++)] Garreau, Alexandre
2018-10-24 16:15   ` Fixed [ Nicolas Goaziou
2018-10-24 16:45     ` Garreau, Alexandre [this message]
2018-10-24 17:25       ` Nicolas Goaziou

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=87h8hb9tv5.fsf@portable.galex-713.eu \
    --to=galex-713@galex-713.eu \
    --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.