From: Noam Postavsky <npostavs@users.sourceforge.net>
To: martin rudalics <rudalics@gmx.at>
Cc: 24368@debbugs.gnu.org
Subject: bug#24368: 25.1; Assertion failure in attach_marker
Date: Tue, 6 Sep 2016 10:50:49 -0400 [thread overview]
Message-ID: <CAM-tV-9CKtRVPbZ6Qm=H4e0_AncExy827ZW98HRpbAb=BRMGZQ@mail.gmail.com> (raw)
In-Reply-To: <57CE65E4.2060105@gmx.at>
On Tue, Sep 6, 2016 at 2:44 AM, martin rudalics <rudalics@gmx.at> wrote:
> We can either make these fail as in the ‘goto-char’ case or handle them
> as with attach_marker.
>
> The former is simpler but would have to be motivated somehow. IMHO
> ‘goto-char’ should not signal an error in that case - it's perfectly
> legitimate to use the position from another buffer's marker as value.
If you want to ignore the marker's buffer you can do (goto-char
(marker-position marker)); if you pass the whole marker object, it
makes sense that the buffer is checked.
next prev parent reply other threads:[~2016-09-06 14:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 7:25 bug#24368: 25.1; Assertion failure in attach_marker martin rudalics
2016-09-05 14:30 ` martin rudalics
2016-09-05 14:35 ` martin rudalics
2016-09-05 14:45 ` martin rudalics
2016-09-05 16:26 ` Eli Zaretskii
2016-09-05 15:04 ` martin rudalics
2016-09-05 16:25 ` Eli Zaretskii
2016-09-05 17:34 ` martin rudalics
2016-09-05 17:52 ` Eli Zaretskii
2016-09-05 17:58 ` martin rudalics
2016-09-05 18:25 ` Eli Zaretskii
2016-09-05 20:28 ` martin rudalics
2016-09-06 6:44 ` martin rudalics
2016-09-06 14:50 ` Noam Postavsky [this message]
2016-09-06 15:35 ` martin rudalics
2016-09-06 15:52 ` Eli Zaretskii
2016-09-06 15:08 ` Eli Zaretskii
2016-09-06 16:09 ` martin rudalics
2016-09-06 16:39 ` Eli Zaretskii
2016-09-06 16:50 ` Eli Zaretskii
2016-09-07 14:52 ` martin rudalics
2016-09-07 15:06 ` Eli Zaretskii
2016-09-07 15:19 ` martin rudalics
2016-09-07 15:47 ` Eli Zaretskii
2016-10-07 8:52 ` martin rudalics
2016-09-06 17:28 ` martin rudalics
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='CAM-tV-9CKtRVPbZ6Qm=H4e0_AncExy827ZW98HRpbAb=BRMGZQ@mail.gmail.com' \
--to=npostavs@users.sourceforge.net \
--cc=24368@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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.