unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark Oteiza <mvoteiza@udel.edu>
To: Andrew Moore <slewsys@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: 26.0.50; CEDET stickyfunc-mode broken after recent removal of default-FOO variables
Date: Wed, 16 Nov 2016 22:00:28 -0500	[thread overview]
Message-ID: <87bmxeu7xv.fsf@udel.edu> (raw)
In-Reply-To: <4EA19C06-5C3C-4A06-B173-370149D65E3A@gmail.com> (Andrew Moore's message of "Wed, 16 Nov 2016 21:32:04 -0500")


Andrew Moore <slewsys@gmail.com> writes:
> CEDET stickyfunc-mode appears to be broken after recent commits:
>
>     e6681b27394a23979c3aef3925f78ef9cd75bd32 (“Nix more uses of default-FOO variables (Bug#24946)”),
>     73d47d22197175f08b2dd62e76d7138872e611d2 (“Remove obsolete default-FOO variables”)
>
> Being enamored of stickyfunc-mode, I’m hoping that someone might point
> me in the direction of a resolution.  What I have so far is only a
> partial workaround.
>
> Prior to the above commits, CEDET and stickyfunc-mode were enabled
> globally via the following lines in my .emacs:
>
>     (load (concat cedet-load-path "/semantic/loaddefs.el"))
>     (semantic-mode)
>     (mapc
>       (lambda (mode)
>         (funcall mode 1))
>       '(global-semantic-idle-summary-mode
>        global-semantic-idle-completions-mode
>        global-semantic-idle-scheduler-mode
>        global-semanticdb-minor-mode))
>        global-semantic-stickyfunc-mode))

Without the cedet-load-path line, the above works fine here (as the sole
contents of init.el) on e6681b27 (the latest commit listed above).  I
can open C files and sticky mode is operational.  Are you loading CEDET
from somewhere else?



  parent reply	other threads:[~2016-11-17  3:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <39BFCECE-1083-4FF2-A3F1-5E8DC10646F1@gmail.com>
2016-11-17  2:32 ` 26.0.50; CEDET stickyfunc-mode broken after recent removal of default-FOO variables Andrew Moore
2016-11-17  2:57   ` Clément Pit--Claudel
2016-11-17  3:00   ` Mark Oteiza [this message]
2016-11-17  5:24     ` Andrew Moore

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=87bmxeu7xv.fsf@udel.edu \
    --to=mvoteiza@udel.edu \
    --cc=emacs-devel@gnu.org \
    --cc=slewsys@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).