‘Top’ vs. ‘bottom’: I think it depends on the work mode. WebClipper and #from-email work like an inbox — items pile up and you want the new one visible at the top. But a bookmark destination, in my use, is often a specific place I’m actively working in — maybe deeply nested inside a list — in a planning/note-taking mode where things mostly grow at the bottom. So “top” doesn’t feel as natural there.
Yes, definitely useful — for a few reasons:
Confirmation — to verify the destination is actually the one I intend before moving.
When I’ve forgotten the number — happens occasionally.
Numbers as shortcuts in the list — even when browsing the picker, the bookmark numbers could still serve as quick-select shortcuts.
Top/bottom option in the picker — the list UI could also be a natural place to choose whether to move to the top or bottom of the target.
We’ve implemented mb shortcut, it is live on beta. Hope, it works as expected.
It does not have the top/bottom option yet, though. Hope to add it later.
Thanks! The dialog looks great; only the bookmark-number shortcut isn’t working smoothly yet.
Priorities are applied. For example, mb6 moves to the bookmark location but also applies “priority 6.”
In the mb dialog, it’s convenient to press the bookmark number to move, but because it moves immediately, I cannot filter by number (for example, by date). I tried typing a space before the number, but that also triggered the move. I’m not sure what the best approach is to preserve both features.
Well, it is embarrassing to miss a problem like this (I mean, setting the priority at the same time as the move is done). But it should be fixed now.
Also, the approach with typing a space before typing a number should now work, too. Not only the space, of course. The presence of any text in the search field will also disable the numeric shortcut.
In the mb dialog text input field, escaping a number-shortcut by prefixing the digit with some character is fine with me, but it may not be obvious or intuitive for others (for example, searching for a date could be a common use case).
I use mb# frequently. It’s really handy. Just to say.
Since moving to a bookmark location is a new use pattern, I recognize that I not only move items but also bookmarks themselves. I have one numbered bookmark reserved as a frequently changing move-target location. But moving a bookmark location needs additional work that slows me down: although a numbered bookmark can be overridden, a plain (unnumbered) bookmark remains at the old location. I need to go to the old location and remove the bookmark, which requires a few steps (or use ab to remove it before assigning it to the new location). For my use cases, when reassigning I never want a bookmark left at the old location.
Moving a numbered bookmark to another location is an interesting scenario, but we’ll probably leave it for a future update.
We’re going to release this update to the production server, too.
Also, we’ve implemented an extra option for Google Calendar integration - synchronising time tag duration with calendar event duration. I.e. if a task marked #3h, then we’ll create a 3-hour event in the Google calendar, and changing such duration will update the time tags in Checkvist.
Not sure if you use Google Calendar integration, but still
It’s interesting how new features like moving content to a bookmark shift the way I work and open the door for follow-ups like moving the bookmark itself. Glad to hear it’s heading to production.
I’m not on Google Calendar anymore and my planning habits have shifted — time-based scheduling tends to be finer-grained than how I use Checkvist. But good to know the duration sync is there if I come back to it.
