bug#19062: closed (25.0.50; `Info-bookmark-jump' changes frames - see FIXME in code)

[GNU bug Tracking System]

Your message dated Wed, 2 Sep 2020 15:19:49 +0000
with message-id 
<CADwFkmkQaPgGev5aWrcQAZ7wJfN+Li9d3iUsBFaUXioD=_1eJw@mail.gmail.com>
and subject line Re: bug#19062: 25.0.50; `Info-bookmark-jump' changes frames - 
see FIXME in code
has caused the debbugs.gnu.org bug report #19062,
regarding 25.0.50; `Info-bookmark-jump' changes frames - see FIXME in code
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
19062: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=19062
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> 25.0.50; `Info-bookmark-jump' changes frames - see FIXME in code
>
>
>
>
> Date: 
>
> Sat, 15 Nov 2014 07:51:58 -0800 (PST)
>
>
>
>
> See the FIXME in the source code.  My setup is too involved to present
> here.  Suffice it to say that the `Info-bookark-jump' code messes with
> the frame that was selected before popping up the Info frame (for
> `Info-find-node').  (I get a separate frame for the Info buffer because
> `special-display-regexps' is `("[ ]?[*][^*]+[*]")'.)
>
>
> In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
>  of 2014-10-20 on LEG570
> Bzr revision: 118168 rgm@gnu.org-20141020195941-icp42t8ttcnud09g
> Windowing system distributor `Microsoft Corp.', version 6.1.7601
> Configured using:
>  `configure --enable-checking=yes,glyphs CPPFLAGS=-DGLYPH_DEBUG=1'
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#19062: 25.0.50; `Info-bookmark-jump' changes frames - see FIXME in code
>
>
>
>
> Date: 
>
> Wed, 2 Sep 2020 15:19:49 +0000
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)
>
>
>
>
> Drew Adams <drew.adams@oracle.com> writes:
>
> > I think the point of the bug report was probably
> > just to point to the FIXME.  Sorry I've forgotten.
>
> No worries, it happens to the best of us.  I think it's enough to track
> that FIXME in the code, and someone will hopefully look into it at some
> undefined point in the future.  That's generally what happens with
> FIXME:s, I guess, until they become an actual issue.
>
> I'm therefore closing this bug report now.  If you encounter any issues
> with this functionality, feel free to reopen or open a new bug.  Thanks.
>
>
> --- End Message ---