
Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
duianto commentedJul 4, 2020
•
edited
When using the search module:
evil-search
And a search prompt is opened:
/
or?
If a window is mouse selected, then the search prompt remains active in the minibuffer.
Now when single pressing a operator key:
c
,d
,y
then it behaves as if it was double pressed:
cc
,dd
,yy
meaning that it acts on the current line.
Reproduction steps
*scratch*
bufferevil-search
by evaluating:
S-M-;
/
or?
With the search module:
evil-search
The search prompt remains active,
but now some evil bindings don't work as expected:
c
works ascc
which deletes the line and enters insert state.d
works asdd
which deletes the line.y
works asyy
which copies the line.With the default search module:
isearch
When mouse selecting another window, then the search prompt closes,
and the evil bindings work as expected.
All three key bindings
c
,d
andy
changes the cursor height to the bottom half,which means that it waits for a motion key to be pressed.
Remaining issue
This PR only solves the issue when mouse selecting another window.
The issue remains if another window is selected with without the mouse:
C-x o
In Spacemacs another window can also be selected with:
M-1
(or another window number)M-m 1
(or another window number)M-m w w
This only happens with the search module:
evil-search
The search prompt closes with the module:
isearch
The evil-search issue has been reported here:
Evil search bug breaks Spacemacs syl20bnr/spacemacs#10410
This is related but it doesn't seem to mention
evil
:https://www.reddit.com/r/emacs/comments/4d8gvt/how_do_i_automatically_close_the_minibuffer_after/
There the suggestion is to use:
I tried changing it to:
But that hook doesn't seem to be called when selecting another window.
I tried adding a message when the
window-configuration-hook
is called,but the message never appears in the messages buffer.
It's docstring says:
So it might only be called when the window configurations are changed.
A sub comment on that reddit thread:
https://www.reddit.com/r/emacs/comments/4d8gvt/how_do_i_automatically_close_the_minibuffer_after/d1p78tl/
suggests using:
focus-out-hook
docstring:
but as the docstring describes it only gets called when Emacs looses focus.
If it was used, then it would add an extra step of switching to another application
and back to Emacs with for example:
M-TAB
(assuming that another application is open).I haven't been able to find a hook that could be used to detect when the minibuffer looses focus.
System info
Evil version 1.14.0
GNU Emacs 26.3 (build 1, x86_64-w64-mingw32) of 2019-08-29
Windows 1903