Commits
- Commit:
36f94f06b08270ab5d4465aa61ae025c98e24c2c
- From:
- Omar Polo <op@omarpolo.com>
- Date:
use the new iri parser in ir_select_gemini
While here also add some error checking.
- Commit:
bd4a08a74023593128f1f6fac9e0f4a093a8441f
- From:
- Omar Polo <op@omarpolo.com>
- Date:
start to refactor the rendering
Previously each vline (visual line) had a full copy of its associated
string, this changes it so it only slices a part of the parent line.
Reduces significantly the memory usage.
This actually worsen the emojify-link glitch reported by Freezr after
the some recent refactoring in the wrapping code. Not a big deal since
I'm about to restructure the whole rendering bit by bit (hopefully!)
- Commit:
8115fd4a99b30c65da4fa4e88552b7aa36b71165
- From:
- Omar Polo <op@omarpolo.com>
- Date:
reset all the state functions regardless of MB_READ vs. MB_COMPLREAD
must_select otherwise is set when MB_COMPREAD but not cleared on
MB_READ, yielding funny errors. While here, move also the other parts
of the state out of the if (MB_COMPLREAD) to avoid this kind of issues
in the future.
- Commit:
f63b8f7342aefba6b3dac50d6790981987c8faa8
- From:
- Omar Polo <op@omarpolo.com>
- Date:
merge the fs into the ui process
The previous separation between the fs and ui process wasn't that good.
The idea was to have a `ui' process tightly sandboxed, but it was a lie
actually. `ui' was one imsg away from making internet connections and
accessing data on the disk, so it wasn't really limited in (almost) any
way.
Furthermore, having to serialize data to/from the fs proc started to
become not really maneagable.
As a first step to fix this situation, join the fs and ui process.
- Commit:
1faa682136aa29eb489b92dcd0e72d28a777f763
- From:
- Omar Polo <op@omarpolo.com>
- Date:
recompute_completions: use the history too when viewing it
- Commit:
3f0b6911f04edeb3b3db82635d5403e519cd365e
- From:
- Omar Polo <op@omarpolo.com>
- Date:
minibuffer_compl_text: honour the history items
- Commit:
0ab6d481eb9306b6f2e175cf1509842e89b173f8
- From:
- Omar Polo <op@omarpolo.com>
- Date:
don't insert current candidate in eecmd_select
after the recent 'must select' thing there's no need to call
minibuffer_insert_current_candidate from eecmd_select anymore.
- Commit:
4bb17137e88ce277e15da09d133b6a3809d26a8a
- From:
- Omar Polo <op@omarpolo.com>
- Date:
readd forgotte NULL check
- Commit:
7c1d55bff32b17bf9ac2b1a374c9cfb98935d847
- From:
- Omar Polo <op@omarpolo.com>
- Date:
readd "select first completion" when must_select is provided
The "don't automatically select the first completion" was a good
change, but for commands that need a must_select policy it's annoying.
This readds the automatic selection but only for those commands.
It's still better than before the changes because now it's clear when
and what gets automatically selected.
- Commit:
27dbcaab4fac08fbb43df9eb5f10781ff7015bb6
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add must_select flag for enter_minibuffer
it only makes sense when entering the minibuffer with completions.
This flag is useful for functions like tag-select where the user types
something but one of the completions *must* be selected.
- Commit:
7bd3a14bde9bd349f4ac2fca9e7f3a1b56ea5d5a
- From:
- Omar Polo <op@omarpolo.com>
- Date:
update the "optional completion" *_select functions
- Commit:
fea02b0bf5e8d28eb46dd51dc411aa2836905b1f
- From:
- Omar Polo <op@omarpolo.com>
- Date:
don't highlight the first completion by deafult
This is the first commit of a series to improve the handling of
completions. Currently it's a mess: some commands look at the
selected entry, others at what was typed in the minibuffer... it's not
clear which commands does what. So, change of defaults: don't
highlight anything by default to avoid confusing the user, C-n and C-p
now are the obvious way to move the focus from the minibuffer to a
completion.
This doesn't change how the commands handle the selection, that will
done in a follow-up commit.
- Commit:
eefb3de54a5e03d944059460fe1caacdb8acb234
- From:
- Omar Polo <op@omarpolo.com>
- Date:
tokenize minibuffer input for better matching
instead of trying to match the given string as-is, split it into
tokens (space-separated words) and try to match those. This allows
to match out of order, for example "mir vid" will match
gemini://vidage.rocks/blog/parliamo-di-mirror.gmi
- Commit:
ed504b9e1a0307a13e869cb3296f07ec072dae42
- From:
- Omar Polo <op@omarpolo.com>
- Date:
reply-last-input: reply input requests on demand
Telescope now remebers the last URL (per tab!) that replied with
1X (input request.) The new command reply-last-input allows to
resend a query to that URL.
It's particularly useful with capsules that make a heavy uses of
10 replies (search engines or similar, interactive pages, etc)
because it both saves a network roundtrip and the user from looking
for the "search" link all across the page ;-)
idea from a conversation with thfr@, thanks!
- Commit:
9d65b1d9ae3209a8a2bc8e8c376dede4f71290ce
- From:
- Omar Polo <op@omarpolo.com>
- Date:
move util.c declarations in utils.h
it's not spelled `util.h' because otherwise it'd get included instead
of /usr/include/util.h