all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nix <nix@esperi.org.uk>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 12869@debbugs.gnu.org
Subject: bug#12869: 24.3.50; 'semantic-change-function' and incremental parsing broken by 'define-obsolete-variable-alias' problems
Date: Mon, 12 Nov 2012 17:35:39 +0000	[thread overview]
Message-ID: <877gpq4tck.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <jwv7gpq7p05.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 12 Nov 2012 11:51:05 -0500")

On 12 Nov 2012, Stefan Monnier told this:

>> Debugger entered--Lisp error: (error "Don't know how to make a localized variable an alias")
>>   defvaralias(semantic-edits-new-change-hooks semantic-edits-new-change-functions nil)
>
> I've changed the code (in emacs-24) to use the new name instead of the
> old one, which I believe should fix this problem.

That means I need to learn enough about bzr to figure out how to get at
that change, doesn't it. I was hoping to avoid that, bzr makes my head
spin in a most unpleasant way.

[...]

OK, I give up. I can't even figure out how to get a log of the branch so
I could dig out the version number, and if I try to check out the branch
in a new directory (just to get the diff of one revision?! how
ridiculous) it wants to download the whole thing from upstream again
even though I'm fairly sure I've already got all those revisions here,
or at least 99.95% of them. Figuring the cause of *that* out requires
digging into the million use cases with confusingly similar names that
bzr has separate independent code for and figuring out which is in use
and life is just. too. short.

> Can you confirm that it fixes your use-case?

If I could figure out how to use blasted bloody hateful bzr, sure.
If you have a diff, I could apply it :)

(aside: I have never encountered another project that does half its work
on release branches and then merges them back to the trunk... but then
this is the only project I've ever seen that tries to use bzr branches
in anger.)





  reply	other threads:[~2012-11-12 17:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-12 14:22 bug#12869: 24.3.50; 'semantic-change-function' and incremental parsing broken by 'define-obsolete-variable-alias' problems Nix
2012-11-12 14:36 ` bug#12869: This regression is not old Nix
2012-11-12 16:51 ` bug#12869: 24.3.50; 'semantic-change-function' and incremental parsing broken by 'define-obsolete-variable-alias' problems Stefan Monnier
2012-11-12 17:35   ` Nix [this message]
2012-11-12 18:22     ` Eli Zaretskii
2012-11-12 19:01       ` Nix
2012-11-12 19:15         ` Eli Zaretskii
2012-11-12 19:14     ` Glenn Morris
2012-11-12 19:15       ` Nix
2012-11-12 19:26   ` Nix
2012-11-12 21:09     ` Stefan Monnier

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=877gpq4tck.fsf@spindle.srvr.nix \
    --to=nix@esperi.org.uk \
    --cc=12869@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.