frameset-to-register: Different from frame-configuration-to-register?

frameset-to-register: Different from frame-configuration-to-register?

[T. V. Raman]

If you do C-x rf to invoke the new frameset-to-register -- and
later attempt to jump to that configuration via C-x rj it throws
an error like so:
this does not happen with the older command
frmae-configuration-to-register.

Debugger entered--Lisp error: (error "Register doesn't contain a buffer position or configuration")
  signal(error ("Register doesn't contain a buffer position or configuration"))
  error("Register doesn't contain a buffer position or configuration")
  #[513 "\301\x02!\302\x01!\203Y\0\211G\303Y\203Y\0\211\304H\b>\203Y\0\211\304H\b>\204&\0\305\306\307\310#\210\211\311H\2043\0\305\312\313\x05!\"\210\211\304H\b>\204A\0\305\306\307\310#\210\211\311H\x01\304H\b>\204R\0\305\306\314\310#\210\x01\315H!\202\362\0\211:\203v\0\316\x01@!\203v\0\317\x01@\x03?\"\210\211\211A@\262\x01b\202\362\0\211:\203\221\0\320\x01@!\203\221\0\321\x01@!\210\211\211A@\262\x01b\202\362\0\322\x01!\203\254\0\323\x01!\204\241\0\305\324!\210\325\323\x02!!\210\211b\202\362\0\211:\203\277\0\211@\326=\203\277\0\327\x01A!\202\362\0\211:\203\357\0\211@\330=\203\357\0\331\x01A@!\204\342\0\332\333\334\x03A@\"!\204\342\0\305\335!\210\327\x01A@!\210\336\x018b\202\362\0\305\337!\207" [cl-struct-registerv-tags get-register vectorp 5 0 error "%s accessing a non-%s" registerv-jump-func registerv 3 "Don't know how to jump to register %s" single-key-description registerv-data 1 frame-configuration-p set-frame-configuration window-configuration-p set-window-configuration markerp marker-buffer "That register's buffer no longer exists" switch-to-buffer file find-file file-query find-buffer-visiting y-or-n-p format "Visit file %s again? " "Register access aborted" 2 "Register doesn't contain a buffer position or configuration"] 8 2384059 (byte-code "\301\302!\bD\207" [current-prefix-arg register-read-with-preview "Jump to register: "] 2)](102 nil)
  ad-Advice-jump-to-register(#[513 "\301\x02!\302\x01!\203Y\0\211G\303Y\203Y\0\211\304H\b>\203Y\0\211\304H\b>\204&\0\305\306\307\310#\210\211\311H\2043\0\305\312\313\x05!\"\210\211\304H\b>\204A\0\305\306\307\310#\210\211\311H\x01\304H\b>\204R\0\305\306\314\310#\210\x01\315H!\202\362\0\211:\203v\0\316\x01@!\203v\0\317\x01@\x03?\"\210\211\211A@\262\x01b\202\362\0\211:\203\221\0\320\x01@!\203\221\0\321\x01@!\210\211\211A@\262\x01b\202\362\0\322\x01!\203\254\0\323\x01!\204\241\0\305\324!\210\325\323\x02!!\210\211b\202\362\0\211:\203\277\0\211@\326=\203\277\0\327\x01A!\202\362\0\211:\203\357\0\211@\330=\203\357\0\331\x01A@!\204\342\0\332\333\334\x03A@\"!\204\342\0\305\335!\210\327\x01A@!\210\336\x018b\202\362\0\305\337!\207" [cl-struct-registerv-tags get-register vectorp 5 0 error "%s accessing a non-%s" registerv-jump-func registerv 3 "Don't know how to jump to register %s" single-key-description registerv-data 1 frame-configuration-p set-frame-configuration window-configuration-p set-window-configuration markerp marker-buffer "That register's buffer no longer exists" switch-to-buffer file find-file file-query find-buffer-visiting y-or-n-p format "Visit file %s again? " "Register access aborted" 2 "Register doesn't contain a buffer position or configuration"] 8 2384059 (byte-code "\301\302!\bD\207" [current-prefix-arg register-read-with-preview "Jump to register: "] 2)] 102 nil)
  apply(ad-Advice-jump-to-register #[513 "\301\x02!\302\x01!\203Y\0\211G\303Y\203Y\0\211\304H\b>\203Y\0\211\304H\b>\204&\0\305\306\307\310#\210\211\311H\2043\0\305\312\313\x05!\"\210\211\304H\b>\204A\0\305\306\307\310#\210\211\311H\x01\304H\b>\204R\0\305\306\314\310#\210\x01\315H!\202\362\0\211:\203v\0\316\x01@!\203v\0\317\x01@\x03?\"\210\211\211A@\262\x01b\202\362\0\211:\203\221\0\320\x01@!\203\221\0\321\x01@!\210\211\211A@\262\x01b\202\362\0\322\x01!\203\254\0\323\x01!\204\241\0\305\324!\210\325\323\x02!!\210\211b\202\362\0\211:\203\277\0\211@\326=\203\277\0\327\x01A!\202\362\0\211:\203\357\0\211@\330=\203\357\0\331\x01A@!\204\342\0\332\333\334\x03A@\"!\204\342\0\305\335!\210\327\x01A@!\210\336\x018b\202\362\0\305\337!\207" [cl-struct-registerv-tags get-register vectorp 5 0 error "%s accessing a non-%s" registerv-jump-func registerv 3 "Don't know how to jump to register %s" single-key-description registerv-data 1 frame-configuration-p set-frame-configuration window-configuration-p set-window-configuration markerp marker-buffer "That register's buffer no longer exists" switch-to-buffer file find-file file-query find-buffer-visiting y-or-n-p format "Visit file %s again? " "Register access aborted" 2 "Register doesn't contain a buffer position or configuration"] 8 2384059 (byte-code "\301\302!\bD\207" [current-prefix-arg register-read-with-preview "Jump to register: "] 2)] (102 nil))
  jump-to-register(102 nil)
  call-interactively(jump-to-register nil nil)
  command-execute(jump-to-register)

Re: frameset-to-register: Different from frame-configuration-to-register?

[Juanma Barranquero]

Package: emacs
Version: 24.3.50

I'm creating a bug report for this, but I am not able to reproduce it.
Could you please answer to the bug thread and put a step-by-step
recipe starting from emacs -Q?

TIA,

   Juanma


---------- Forwarded message ----------
From: T. V. Raman <tv.raman.tv@gmail.com>
Date: Sat, Feb 8, 2014 at 8:31 PM
Subject: frameset-to-register: Different from frame-configuration-to-register?
To: emacs-devel@gnu.org


If you do C-x rf to invoke the new frameset-to-register -- and
later attempt to jump to that configuration via C-x rj it throws
an error like so:
this does not happen with the older command
frmae-configuration-to-register.

Debugger entered--Lisp error: (error "Register doesn't contain a
buffer position or configuration")
  signal(error ("Register doesn't contain a buffer position or configuration"))
  error("Register doesn't contain a buffer position or configuration")
  #[513 "\301 !\302 !\203Y \211G\303Y\203Y \211\304H >\203Y \211\304H
>\204& \305\306\307\310#\210\211\311H\2043 \305\312\313
!\"\210\211\304H >\204A \305\306\307\310#\210\211\311H \304H >\204R
\305\306\314\310#\210 \315H!\202\362 \211:\203v \316 @!\203v \317 @
?\"\210\211\211A@\262 b\202\362 \211:\203\221 \320 @!\203\221 \321
@!\210\211\211A@\262 b\202\362 \322 !\203\254 \323 !\204\241
\305\324!\210\325\323 !!\210\211b\202\362 \211:\203\277
\211@\326=\203\277 \327 A!\202\362 \211:\203\357 \211@\330=\203\357
\331 A@!\204\342 \332\333\334 A@\"!\204\342 \305\335!\210\327
A@!\210\336 8b\202\362 \305\337!\207" [cl-struct-registerv-tags
get-register vectorp 5 0 error "%s accessing a non-%s"
registerv-jump-func registerv 3 "Don't know how to jump to register
%s" single-key-description registerv-data 1 frame-configuration-p
set-frame-configuration window-configuration-p
set-window-configuration markerp marker-buffer "That register's buffer
no longer exists" switch-to-buffer file find-file file-query
find-buffer-visiting y-or-n-p format "Visit file %s again? " "Register
access aborted" 2 "Register doesn't contain a buffer position or
configuration"] 8 2384059 (byte-code "\301\302! D\207"
[current-prefix-arg register-read-with-preview "Jump to register: "]
2)](102 nil)
  ad-Advice-jump-to-register(#[513 "\301 !\302 !\203Y \211G\303Y\203Y
\211\304H >\203Y \211\304H >\204& \305\306\307\310#\210\211\311H\2043
\305\312\313 !\"\210\211\304H >\204A \305\306\307\310#\210\211\311H
\304H >\204R \305\306\314\310#\210 \315H!\202\362 \211:\203v \316
@!\203v \317 @ ?\"\210\211\211A@\262 b\202\362 \211:\203\221 \320
@!\203\221 \321 @!\210\211\211A@\262 b\202\362 \322 !\203\254 \323
!\204\241 \305\324!\210\325\323 !!\210\211b\202\362 \211:\203\277
\211@\326=\203\277 \327 A!\202\362 \211:\203\357 \211@\330=\203\357
\331 A@!\204\342 \332\333\334 A@\"!\204\342 \305\335!\210\327
A@!\210\336 8b\202\362 \305\337!\207" [cl-struct-registerv-tags
get-register vectorp 5 0 error "%s accessing a non-%s"
registerv-jump-func registerv 3 "Don't know how to jump to register
%s" single-key-description registerv-data 1 frame-configuration-p
set-frame-configuration window-configuration-p
set-window-configuration markerp marker-buffer "That register's buffer
no longer exists" switch-to-buffer file find-file file-query
find-buffer-visiting y-or-n-p format "Visit file %s again? " "Register
access aborted" 2 "Register doesn't contain a buffer position or
configuration"] 8 2384059 (byte-code "\301\302! D\207"
[current-prefix-arg register-read-with-preview "Jump to register: "]
2)] 102 nil)
  apply(ad-Advice-jump-to-register #[513 "\301 !\302 !\203Y
\211G\303Y\203Y \211\304H >\203Y \211\304H >\204&
\305\306\307\310#\210\211\311H\2043 \305\312\313 !\"\210\211\304H
>\204A \305\306\307\310#\210\211\311H \304H >\204R
\305\306\314\310#\210 \315H!\202\362 \211:\203v \316 @!\203v \317 @
?\"\210\211\211A@\262 b\202\362 \211:\203\221 \320 @!\203\221 \321
@!\210\211\211A@\262 b\202\362 \322 !\203\254 \323 !\204\241
\305\324!\210\325\323 !!\210\211b\202\362 \211:\203\277
\211@\326=\203\277 \327 A!\202\362 \211:\203\357 \211@\330=\203\357
\331 A@!\204\342 \332\333\334 A@\"!\204\342 \305\335!\210\327
A@!\210\336 8b\202\362 \305\337!\207" [cl-struct-registerv-tags
get-register vectorp 5 0 error "%s accessing a non-%s"
registerv-jump-func registerv 3 "Don't know how to jump to register
%s" single-key-description registerv-data 1 frame-configuration-p
set-frame-configuration window-configuration-p
set-window-configuration markerp marker-buffer "That register's buffer
no longer exists" switch-to-buffer file find-file file-query
find-buffer-visiting y-or-n-p format "Visit file %s again? " "Register
access aborted" 2 "Register doesn't contain a buffer position or
configuration"] 8 2384059 (byte-code "\301\302! D\207"
[current-prefix-arg register-read-with-preview "Jump to register: "]
2)] (102 nil))
  jump-to-register(102 nil)
  call-interactively(jump-to-register nil nil)
  command-execute(jump-to-register)

Re: frameset-to-register: Different from frame-configuration-to-register?

[raman]

To repro, make sure you switch buffers etc after invoking C-x rf so the
config you jump to with C-x rj is different from your current setup.

So repro steps:

1. M-x calendar
2. C-x4b *scratch*
3. C-xrf a
4. M-x shell
5. C-x 1
6. C-xrj a

Re filing a detailed bug report, I've stayed away because I was afraid
I'd not be able to do that from the comfort of Emacs -- 

bug#16696: Fwd: frameset-to-register: Different from frame-configuration-to-register?

[Juanma Barranquero]

Following your recipe, I do not see the same error that you reported.
I get a message "Marker points into wrong buffer: #<marker at 192 in
*scratch*>", but the frame is restored. I'll have to look into it.

As for making a bug report, it already exists and it's bug#16696 (I'm
forwarding this message to that bug thread). Please answer any
followup comment there and not to emacs-devel.

Thanks,

     Juanma


---------- Forwarded message ----------
From: raman <tv.raman.tv@gmail.com>
Date: Sun, Feb 9, 2014 at 11:01 PM
Subject: Re: frameset-to-register: Different from
frame-configuration-to-register?
To: emacs.devel@gnu.org


To repro, make sure you switch buffers etc after invoking C-x rf so the
config you jump to with C-x rj is different from your current setup.

So repro steps:

1. M-x calendar
2. C-x4b *scratch*
3. C-xrf a
4. M-x shell
5. C-x 1
6. C-xrj a

Re filing a detailed bug report, I've stayed away because I was afraid
I'd not be able to do that from the comfort of Emacs --

bug#16696: Fwd: frameset-to-register: Different from frame-configuration-to-register?

[Juanma Barranquero]

I've fixed the bug I was able to reproduce. Could you please try to
reproduce your problem with the current trunk?

Thanks.

Re: frameset-to-register: Different from frame-configuration-to-register?

[Glenn Morris]

raman wrote:

> Re filing a detailed bug report, I've stayed away because I was afraid
> I'd not be able to do that from the comfort of Emacs -- 

"Filing a detailed bug report" means sending a clear description to
bug-gnu-emacs@gnu.org. So you just need to change the address to which
you send mail, and be more informative. The emacs-devel mailing list is
not meant for bug reporting.

bug#16696: Fwd: frameset-to-register: Different from frame-configuration-to-register?

[Juanma Barranquero]

On Thu, Feb 13, 2014 at 3:36 AM, T. V. Raman <tv.raman.tv@gmail.com> wrote:

> works.

Great. Closing.