helm-show-kill-ring: void-variable \.\.\. #94

Closed
fgeller opened this Issue Aug 8, 2012 · 10 comments

Comments

Projects
None yet
5 participants
@fgeller

fgeller commented Aug 8, 2012

No description provided.

@fgeller

This comment has been minimized.

Show comment
Hide comment
@fgeller

fgeller Aug 8, 2012

Hi,

sorry but somehow my comment was eaten by some octocat.

Here goes:

I'v upgraded to helm-20120807 and helm-show-kill-ring now fails with the following backtrace:

Debugger entered--Lisp error: (void-variable \.\.\.)
  (helm-attrset \.\.\. last-command)
  (lambda nil (helm-attrset \.\.\. last-command))()
  apply((lambda nil (helm-attrset \.\.\. last-command)) nil)
  helm-funcall-with-source(((match helm-mp-exact-match helm-mp-3-match) (search helm-mp-ex
  helm-funcall-foreach(init)
  helm-initial-setup()
  helm-initialize(nil nil ((name . "Kill Ring") (init lambda nil (helm-attrset \.\.\. last
  byte-code([snip -- octocats don's like escape seqs?]
  byte-code([snip -- octocats don's like escape seqs?]
  helm-internal(((name . "Kill Ring") (init lambda nil (helm-attrset \.\.\. last-command))
  apply(helm-internal (((name . "Kill Ring") (init lambda nil (helm-attrset \.\.\. last-co
  helm(((name . "Kill Ring") (init lambda nil (helm-attrset \.\.\. last-command)) (candida
  apply(helm (((name . "Kill Ring") (init lambda nil (helm-attrset \.\.\. last-command)) (
  #[nil "\302�\303\304  \"\"\207" [fn helm-argument-keys apply mapcar #[(key) "\302�    \"
  helm-let-internal(((helm-allow-nest . t)) #[nil "\302�\303\304    \"\"\207" [fn helm-arg
  helm(:sources ((name . "Kill Ring") (init lambda nil (helm-attrset \.\.\. last-command))
  helm-show-kill-ring()
  call-interactively(helm-show-kill-ring nil nil)

(Truncated at 90 characters for brevity)

Do you have any idea what's wrong? FWIW, I don't see any kill-ring specific customization in my configuration...

Thanks in advance!

fgeller commented Aug 8, 2012

Hi,

sorry but somehow my comment was eaten by some octocat.

Here goes:

I'v upgraded to helm-20120807 and helm-show-kill-ring now fails with the following backtrace:

Debugger entered--Lisp error: (void-variable \.\.\.)
  (helm-attrset \.\.\. last-command)
  (lambda nil (helm-attrset \.\.\. last-command))()
  apply((lambda nil (helm-attrset \.\.\. last-command)) nil)
  helm-funcall-with-source(((match helm-mp-exact-match helm-mp-3-match) (search helm-mp-ex
  helm-funcall-foreach(init)
  helm-initial-setup()
  helm-initialize(nil nil ((name . "Kill Ring") (init lambda nil (helm-attrset \.\.\. last
  byte-code([snip -- octocats don's like escape seqs?]
  byte-code([snip -- octocats don's like escape seqs?]
  helm-internal(((name . "Kill Ring") (init lambda nil (helm-attrset \.\.\. last-command))
  apply(helm-internal (((name . "Kill Ring") (init lambda nil (helm-attrset \.\.\. last-co
  helm(((name . "Kill Ring") (init lambda nil (helm-attrset \.\.\. last-command)) (candida
  apply(helm (((name . "Kill Ring") (init lambda nil (helm-attrset \.\.\. last-command)) (
  #[nil "\302�\303\304  \"\"\207" [fn helm-argument-keys apply mapcar #[(key) "\302�    \"
  helm-let-internal(((helm-allow-nest . t)) #[nil "\302�\303\304    \"\"\207" [fn helm-arg
  helm(:sources ((name . "Kill Ring") (init lambda nil (helm-attrset \.\.\. last-command))
  helm-show-kill-ring()
  call-interactively(helm-show-kill-ring nil nil)

(Truncated at 90 characters for brevity)

Do you have any idea what's wrong? FWIW, I don't see any kill-ring specific customization in my configuration...

Thanks in advance!

@lewang

This comment has been minimized.

Show comment
Hide comment
@lewang

lewang Aug 8, 2012

Member

Do you use session.el?

Member

lewang commented Aug 8, 2012

Do you use session.el?

@fgeller

This comment has been minimized.

Show comment
Hide comment

fgeller commented Aug 8, 2012

Yes...

@thierryvolpiatto

This comment has been minimized.

Show comment
Hide comment
@thierryvolpiatto

thierryvolpiatto Aug 8, 2012

Member

fgeller notifications@github.com writes:

Do you have any idea what's wrong? FWIW, I don't see any kill-ring
specific customization in my configuration...
Can't reproduce here.
Please try from ./emacs-helm.sh from your helm directory (or emacs -Q
and install basic helm config).


Reply to this email directly or view it on GitHub:
#94 (comment)

Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997

Member

thierryvolpiatto commented Aug 8, 2012

fgeller notifications@github.com writes:

Do you have any idea what's wrong? FWIW, I don't see any kill-ring
specific customization in my configuration...
Can't reproduce here.
Please try from ./emacs-helm.sh from your helm directory (or emacs -Q
and install basic helm config).


Reply to this email directly or view it on GitHub:
#94 (comment)

Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997

@thierryvolpiatto

This comment has been minimized.

Show comment
Hide comment
@thierryvolpiatto

thierryvolpiatto Aug 8, 2012

Member

Also, what binding do you use to call helm-show-kill-ring?
Maybe C-y or M-y?
If so, try (with your full config this time not emacs -Q), to call the helm-show-kill-ring from M-x and not from C or M-y.

Member

thierryvolpiatto commented Aug 8, 2012

Also, what binding do you use to call helm-show-kill-ring?
Maybe C-y or M-y?
If so, try (with your full config this time not emacs -Q), to call the helm-show-kill-ring from M-x and not from C or M-y.

@lewang

This comment has been minimized.

Show comment
Hide comment
@lewang

lewang Aug 8, 2012

Member

This is an issue with how session.el saves variables to file. It abbreviates with "..." when the level is too deep or length too long.

See the variable session-save-print-spec

I have this in my init:

(setq session-save-print-spec '(t nil 40000))

To confirm this is the problem, check for "..." in your session saved file. You should find it in the kill-ring variable.

Member

lewang commented Aug 8, 2012

This is an issue with how session.el saves variables to file. It abbreviates with "..." when the level is too deep or length too long.

See the variable session-save-print-spec

I have this in my init:

(setq session-save-print-spec '(t nil 40000))

To confirm this is the problem, check for "..." in your session saved file. You should find it in the kill-ring variable.

@fgeller

This comment has been minimized.

Show comment
Hide comment
@fgeller

fgeller Aug 8, 2012

@lewang thanks a lot -- that was it! sorry, that I didn't catch that after your first question..

please close at will :)

fgeller commented Aug 8, 2012

@lewang thanks a lot -- that was it! sorry, that I didn't catch that after your first question..

please close at will :)

@thierryvolpiatto

This comment has been minimized.

Show comment
Hide comment
@thierryvolpiatto

thierryvolpiatto Aug 8, 2012

Member

Ok so I close this bug, thanks to you fgeller and Le.

Member

thierryvolpiatto commented Aug 8, 2012

Ok so I close this bug, thanks to you fgeller and Le.

@elim

This comment has been minimized.

Show comment
Hide comment
@elim

elim Nov 6, 2012

I also was saved by this information. Thank you :octocat: 🌟

elim commented Nov 6, 2012

I also was saved by this information. Thank you :octocat: 🌟

@zw963

This comment has been minimized.

Show comment
Hide comment
@zw963

zw963 May 21, 2016

Contributor

Cool, this is worked for me now.

Though, we need delete ~/.emacs.d/.session and force kill emacs (kill -9 emacs) at first.
and then, start emac as usual with new config, everthing is fine.

Contributor

zw963 commented May 21, 2016

Cool, this is worked for me now.

Though, we need delete ~/.emacs.d/.session and force kill emacs (kill -9 emacs) at first.
and then, start emac as usual with new config, everthing is fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment