Almost there! Everything looks great except selecting text, where I am 
still unable to read the text that is selected because both the highlight 
and the text are light-colored:

[image: bad-highlight.png]

BTW, if you have trouble reproducing you can find a trimmed-down copy of 
the wiki I've been testing with here 
<https://github.com/sobjornstad/zettelkasten-sib/blob/master/index.html>. 
Should have mentioned that before.

On Saturday, December 5, 2020 at 11:15:40 AM UTC-6 BurningTreeC wrote:

> @Soren Bjornstad, the issues with the vim keymap and the palette colors 
> should now be resolved
>
> all the best, BTC
>
> Soren Bjornstad schrieb am Freitag, 4. Dezember 2020 um 03:41:39 UTC+1:
>
>> @BurningTreeC: Thanks for looking into this! What's up there now is 
>> definitely an improvement, but the colors are still really wonky compared 
>> to 5.1.22.
>>
>> First, the colors (at least on the Nord palette) now make it extremely 
>> difficult to see through the cursor, presumably because the background is 
>> now dark so the same highlight color doesn't look good.
>> [image: block.png]
>>
>> Second, the highlight applied to matching brackets doesn't line up top to 
>> bottom. Maybe this is intentional so it's easier to tell which one is the 
>> cursor and which is the match, but to my eyes it looks a bit odd:
>> [image: colors.png]
>> Previously the other bracket changed color and the background stayed the 
>> same, like this:
>> [image: 2.png]
>> Last, any text highlighted with the mouse or in visual mode is another 
>> hard-to-read color:
>>
>> [image: selection.png]
>>
>>
>> On Thursday, December 3, 2020 at 11:01:10 AM UTC-6 BurningTreeC wrote:
>>
>>> @Soren Bjornstad,
>>>
>>> the vim keymap should now work like expected on the current prerelease
>>>
>>> Soren Bjornstad schrieb am Dienstag, 1. Dezember 2020 um 17:14:36 UTC+1:
>>>
>>>> I use the vim keymapping with CodeMirror. After upgrading, when I'm in 
>>>> normal mode and the cursor is supposed to display as a block, it is 
>>>> instead 
>>>> completely invisible. It looks normal when it's in I-beam mode. I am 
>>>> guessing this is related to theming the text input area. The issue is not 
>>>> confined to a specific palette.
>>>>
>>>> Obviously, the editor is just about unusable in this state.
>>>>
>>>> Can anyone else reproduce this, or is it something weird with my wiki?
>>>>
>>>> On Monday, November 30, 2020 at 5:36:42 AM UTC-6 [email protected] 
>>>> wrote:
>>>>
>>>>> I’m hoping that we’ll be able to release v5.1.23 of TiddlyWiki towards 
>>>>> the end of this week. There’s some discussion over on GitHub about the 
>>>>> last 
>>>>> few loose ends to be tied up:
>>>>>
>>>>> https://github.com/Jermolene/TiddlyWiki5/issues/5130
>>>>>
>>>>> The most important call to action is for developers of plugins and 
>>>>> adaptations to take this opportunity to verify that the new release 
>>>>> doesn’t 
>>>>> break anything.
>>>>>
>>>>> The second call to action is for as many people as possible to put the 
>>>>> new release through it’s paces by performing a test upgrade of the wikis 
>>>>> that are important to them. Don’t switch over to the new version yet, of 
>>>>> course.
>>>>>
>>>>> You can upgrade single file wikis here:
>>>>>
>>>>> https://tiddlywiki.com/prerelease/upgrade.html
>>>>>
>>>>> This is a really quite a massive release, with over 160 new features 
>>>>> listed in the release note. (I am working on improvements to the 
>>>>> presentation of the release note, it’s a bit of a wall of text right now).
>>>>>
>>>>> https://tiddlywiki.com/prerelease/
>>>>>
>>>>> Just to mention a handful of new features that I’m particularly 
>>>>> excited about:
>>>>>
>>>>> * Keyboard support for the main core dropdowns: search, new tag, 
>>>>> tiddler type, new field, and the “link” button in the editor toolbar
>>>>>
>>>> * The beginnings of support for switchable page templates (referred to 
>>>>> as layouts), which will give us a route to introduce a more modern 
>>>>> alternative layout
>>>>>
>>>> * The ability to rename tiddlers during the import process (and to 
>>>>> easily see which incoming tiddlers will overwrite existing tiddlers)
>>>>> * Many new filter operators that together make the TiddlyWiki filter 
>>>>> language significantly more powerful and expressive
>>>>> * Improvements to the “tm-scroll” message making it possible to scroll 
>>>>> to positions within a tiddler
>>>>> * Via the JSZip plugin, the ability to dynamically create ZIP files, 
>>>>> giving us the ability to create static sites in the browser
>>>>> * New <$action-log> and <$log> widgets to aid debugging
>>>>>
>>>>> There are many, many bug fixes and other improvements too.
>>>>>
>>>>> As ever, I’m profoundly grateful to all the contributors who have 
>>>>> pulled together to make this such an exciting release. You can see here 
>>>>> how 
>>>>> much activity there’s been since v5.1.22:
>>>>>
>>>>>
>>>>> https://github.com/Jermolene/TiddlyWiki5/graphs/contributors?from=2020-04-16&to=2020-11-30&type=c
>>>>>
>>>>> My own contribution graph (below) shows nicely how this release covers 
>>>>> my illness and recovery from COVID, and undoubtedly a strange and painful 
>>>>> time for all of us. I couldn’t be more pleased that this community has 
>>>>> thrived, and seems to be working together so well at the moment.
>>>>>
>>>>> Please respond with any questions and thoughts here.
>>>>>
>>>>> Best wishes
>>>>>
>>>>> Jeremy.
>>>>>
>>>>>
>>>>>
>>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/8bbb9061-4ab2-43f5-ab39-e79e8cf0a970n%40googlegroups.com.

Reply via email to