unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "J.P." <jp@neverwas.me>
To: Rostislav Svoboda <rostislav.svoboda@gmail.com>
Cc: 51841@debbugs.gnu.org, emacs-erc@gnu.org
Subject: bug#51841: 27.2; erc-insert-marker has no value
Date: Sun, 14 Nov 2021 14:53:35 -0800	[thread overview]
Message-ID: <87r1bixsb4.fsf__17876.3902209297$1636930460$gmane$org@neverwas.me> (raw)
In-Reply-To: <CAEtmmez_8z9kU1orMBmgPBbOdrS28p2v68e0oYG6k0JGY_zrzA@mail.gmail.com> (Rostislav Svoboda's message of "Sun, 14 Nov 2021 14:19:31 +0100")

Rostislav Svoboda <rostislav.svoboda@gmail.com> writes:

> Hi. The bug
>     "erc-insert-marker has no value, please report a bug"
> gets triggered when I run `M-x erc-mode` in an existing IRC channel.
>
> Thanks in advance for fixing it.
>
> Bost

Hi Bost,

I think what's happening is that all your local variables are getting
killed by manually running `erc-mode'. And replacements are hard won
because ERC is a bit funny when it comes to setting up buffers and
initializing local variables. This causes real problems, like imposing
artificial burdens on modules, for example. (I have a patch that I think
improves the situation here [1], but that's a whole other discussion.)

The error you saw is from the function `erc-beg-of-input-line', which is
used throughout ERC. That message probably wasn't intended for folks
invoking `erc-mode' manually, which you've probably gathered by now.
However, you're welcome to share whatever it was that drove you to try
that in the first place, if you think there's more to consider here.

Thanks,
J.P.

[1] https://gitlab.com/jpneverwas/erc-tools/-/raw/39b10aa2a1832586aeef34b9a6f045d6e0f9b015/bugs/49860/patches/wip/0024-Enable-local-ERC-modules-in-erc-mode-buffers.patch





  reply	other threads:[~2021-11-14 22:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-14 13:19 bug#51841: 27.2; erc-insert-marker has no value Rostislav Svoboda
2021-11-14 22:53 ` J.P. [this message]
     [not found] ` <87r1bixsb4.fsf@neverwas.me>
2021-11-14 23:29   ` Rostislav Svoboda
     [not found]   ` <CAEtmmey6kqfNNKtX6+QDwMEGTtS=eOmCYa1HRY1KivXRfwQT5Q@mail.gmail.com>
2021-11-15  9:08     ` Lars Ingebrigtsen
     [not found]     ` <87ilwtzszy.fsf@gnus.org>
2021-11-15 10:23       ` J.P.
     [not found]       ` <87v90tra36.fsf@neverwas.me>
2021-11-15 12:12         ` Rostislav Svoboda
     [not found]         ` <CAEtmmezk406mKS9VU4pdU5g4+7_O5HLzTeSsZ=E2ArC57WPyHg@mail.gmail.com>
2021-11-15 15:12           ` J.P.
2021-11-18 14:49           ` J.P.
     [not found]           ` <87v90pzfgn.fsf@neverwas.me>
2021-11-19  3:13             ` J.P.
     [not found]             ` <87o86gn8gs.fsf@neverwas.me>
2021-11-19  5:28               ` Lars Ingebrigtsen
     [not found]               ` <87tug8yaqz.fsf@gnus.org>
2021-11-19 10:45                 ` J.P.

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='87r1bixsb4.fsf__17876.3902209297$1636930460$gmane$org@neverwas.me' \
    --to=jp@neverwas.me \
    --cc=51841@debbugs.gnu.org \
    --cc=emacs-erc@gnu.org \
    --cc=rostislav.svoboda@gmail.com \
    /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.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).