Update beframe to version 1.0.0
Add missing dates to the changelog
Simplify how frames are set up
This ensures that the functions we call with a FRAME argument are
evaluated in the desired order.
Simplify how project frames are named
I am removing the experiment with the added symbol, because my intent
was to have it as purely decorative. But this was actually writing it
as part of the name itself.
Ensure project--list has a list value
By default, it is set to 'unset', which produces an error in
'beframe-infer-frame-name'.
Merge branch 'refinements'
Simplify 'beframe--buffers-name-to-objects'
Simplify 'beframe--buffer-names-consolidated'
Simplify 'beframe-buffer-names'
Make sure 'beframe-global-buffers' accepts a nil value
Reword the manual's documentation of 'beframe-global-buffers'
Make 'beframe-rename-frame' apply a symbol to projects
This happens when 'beframe-rename-frame' is called from Lisp, per the
user option 'beframe-rename-function' when 'beframe-mode' is enabled.
Do not disable menu bar beframe-buffer-menu entry even with single frame
The reason is that even if we only have a single frame, it can still
have its own beframed buffer list. This happens when we create a new
frame, close the others, and now have access only to the buffers
visited from the new frame. As always, the global buffer list is
still available, though it has to be accessed with commands other than
those of Beframe (e.g. 'consult-buffer' from the 'consult' package).
Place the menu inside of "Buffers"; rename it to stand out
Unassume the buffer of the latest frame
We do not want to have the current buffer from where a new frame was
created into the buffer list of that frame.
Do not prompt for FRAME if only 1; return user-error
Fix beframe--assume doc string
Acknowledge Edgar Vincent for commit 77cc30c
The change is below the ~15 lines of changes and so Edgar does not
need to assign copyright to the Free Software Foundation.