emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: emacs-orgmode@gnu.org
Subject: Re: user-error: Not at a block -- how to debug?
Date: Mon, 15 Sep 2014 17:09:23 +0100	[thread overview]
Message-ID: <87y4tkoogc.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87a961ktf4.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Mon, 15 Sep 2014 13:35:43 +0200")

[-- Attachment #1: Type: text/plain, Size: 737 bytes --]

Nicolas,

again, thanks for fixing this bug but I wonder if you would mind
thinking about the approach to error handling.  The user error handling
was short-circuiting the normal file handling, in particular some of the
hooks and other processing that would have been expected to be
invoked.  In this case, I had used recentf to visit the file.  Because
of the user error, the buffer wouldn't appear at all.  Likewise,
projectile processing was being terminated.  Both aspects caused me some
confusion, to say the least...

Is there an alternative means of raising an error or warning without
terminating normal processing?

thanks,
eric

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 24.3.1, Org release_8.3beta-265-g7cf7e4

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 180 bytes --]

  parent reply	other threads:[~2014-09-15 16:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-15  9:44 user-error: Not at a block -- how to debug? Eric S Fraga
2014-09-15 10:32 ` Thorsten Jolitz
2014-09-15 10:45   ` Eric S Fraga
2014-09-15 11:35     ` Nicolas Goaziou
2014-09-15 16:02       ` Eric S Fraga
2014-09-15 16:09       ` Eric S Fraga [this message]
2014-09-15 18:28         ` Nicolas Goaziou
2014-09-15 10:36 ` Eric S Fraga, Eric S Fraga
2014-09-15 10:53 ` Andrea Rossetti
2014-09-15 16:03   ` Eric S Fraga

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=87y4tkoogc.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.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).