Hello Edward,

I'm using Leo since a long time as my Outliner to keep track of interesting 
blog entries & sites.

Recently I found an interesting blog entry about 'Django: one ORM to rule 
all databases' [1].

When I documented it in my daily log-entry I noticed that Leo's key 
handling got confused with the content of this node.

This cought my attention - and - I created a minimal test-outline (see 
attachment).

You should be able to reproduce it yourself, if you open the outline - and 
- enter a new line at the end of the '@rst TN-2025-10-16-o.html' node for 
example.

* The cursor position moves back by one for every 'leading' Unicode Emoji 
...

Using this test-outline I found out, that ...

* I'm able to reproduce this issue with 'Leo' on Linux - and - Windows - 
BUT -
* I'm NOT able to reproduce it with 'LeoInteg' and 'LeoServer'.

Finally my question: Is this something that is important enough to be 
tracked & possibly resolved ?

With kind regards,

Viktor
---
PS: The author of the blog entry has in the mean-time removed all 'leading' 
Unicode Emoji's from each headline. - I was just lucky ( - or - unfortunate 
enough ;-) to copy an early / initial state.
---
[1] Django: one ORM to rule all databases πŸ’

* https://www.paulox.net/2025/10/06/django-orm-comparison/
---

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/leo-editor/8c2685bb-b0af-4b8f-80c9-e0394664f52dn%40googlegroups.com.
<?xml version="1.0" encoding="utf-8"?>
<!-- Created by Leo: https://leo-editor.github.io/leo-editor/leo_toc.html -->
<leo_file xmlns:leo="https://leo-editor.github.io/leo-editor/namespaces/leo-python-editor/1.1"; >
<leo_header file_format="2"/>
<globals/>
<preferences/>
<find_panel_settings/>
<vnodes>
<v t="user.20200301210405.1"><vh>Test Outline for 2025</vh>
<v t="user.20251005201305.1"><vh>@rst TN-2025-10-06.html</vh>
<v t="user.20251005201305.3"><vh>Test node content ...</vh></v>
</v>
<v t="user.20251016102412.1"><vh>@rst TN-2025-10-16-a.html</vh>
<v t="user.20251016102412.2"><vh>Test node content ...</vh></v>
</v>
<v t="user.20251016102642.1"><vh>@rst TN-2025-10-16-b.html</vh>
<v t="user.20251016102642.2"><vh>Test node content ...</vh></v>
</v>
<v t="user.20251016102832.1"><vh>@rst TN-2025-10-16-c.html</vh>
<v t="user.20251016102832.2"><vh>Test node content ...</vh></v>
</v>
<v t="user.20251016103732.1"><vh>@rst TN-2025-10-16-o.html</vh>
<v t="user.20251016103732.2"><vh>Test node content ...</vh></v>
</v>
</v>
</vnodes>
<tnodes>
<t tx="user.20200301210405.1">@language rest
@tabwidth -4
@path ./TO/2025/
</t>
<t tx="user.20251005201305.1">====================
Test-Node 2025-10-06
====================

.. contents::
   :depth: 2
</t>
<t tx="user.20251005201305.3">Django: one ORM to rule all databases πŸ’

* From the 'Python community' feeds
* https://www.paulox.net/2025/10/06/django-orm-comparison/
* -&gt; 🌐 Introduction
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#introduction
* -&gt; πŸ›οΈ Database comparison
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#database-comparison
* -&gt; 🌈 Inspiration
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#inspiration
* -&gt; 🎯 Why this matrix?
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#why-this-matrix
* -&gt; ⚠️ Disclaimer
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#disclaimer
* -&gt; πŸ“Š Django ORM feature support table
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#django-orm-feature-support-table
* -&gt; πŸ‘€ At-a-glance
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#at-a-glance
* -&gt; πŸ€” About this comparison
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#about-this-comparison
* -&gt; πŸ§‘β€πŸ’» Example: full-text search
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#example-full-text-search
* -&gt; πŸ¦‰ History Bits
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#history-bits
* -&gt; ✨ Idea spark
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#idea-spark
* -&gt; πŸ—£οΈ Community feedback
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#community-feedback
* -&gt; πŸš€ What’s next?
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#whats-next
* -&gt; πŸ—£οΈ Call to action
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#call-to-action
* -&gt; πŸ”— References
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#references

*TODO: Analyze why Leo's ~ key handling ~ gets confused - Done?*
</t>
<t tx="user.20251016102412.1">======================
Test-Node 2025-10-16-a
======================

.. contents::
   :depth: 2
</t>
<t tx="user.20251016102412.2">Django: one ORM to rule all databases πŸ’

* From the 'Python community' feeds
* https://www.paulox.net/2025/10/06/django-orm-comparison/
* -&gt; 🌐 Introduction
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#introduction

*TODO: Analyze why Leo's ~ key handling ~ gets confused - Done?*
</t>
<t tx="user.20251016102642.1">======================
Test-Node 2025-10-16-b
======================

.. contents::
   :depth: 2
</t>
<t tx="user.20251016102642.2">Django: one ORM to rule all databases πŸ’

* From the 'Python community' feeds
* https://www.paulox.net/2025/10/06/django-orm-comparison/
* -&gt; 🌐 Introduction
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#introduction
* -&gt; πŸ›οΈ Database comparison
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#database-comparison

*TODO: Analyze why Leo's ~ key handling ~ gets confused - Done?*
</t>
<t tx="user.20251016102832.1">======================
Test-Node 2025-10-16-c
======================

.. contents::
   :depth: 2
</t>
<t tx="user.20251016102832.2">Django: one ORM to rule all databases πŸ’

* From the 'Python community' feeds
* https://www.paulox.net/2025/10/06/django-orm-comparison/
* -&gt; 🌐 Introduction
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#introduction
* -&gt; πŸ›οΈ Database comparison
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#database-comparison
* -&gt; 🌈 Inspiration
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#inspiration

*TODO: Analyze why Leo's ~ key handling ~ gets confused - Done?*
</t>
<t tx="user.20251016103732.1">======================
Test-Node 2025-10-16-o
======================

.. contents::
   :depth: 2
</t>
<t tx="user.20251016103732.2">Django: one ORM to rule all databases πŸ’

* From the 'Python community' feeds
* https://www.paulox.net/2025/10/06/django-orm-comparison/
* -&gt; 🌐 Introduction
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#introduction
* -&gt; πŸ›οΈ Database comparison
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#database-comparison
* -&gt; 🌈 Inspiration
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#inspiration
* -&gt; 🎯 Why this matrix?
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#why-this-matrix
* -&gt; ⚠️ Disclaimer
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#disclaimer
* -&gt; πŸ“Š Django ORM feature support table
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#django-orm-feature-support-table
* -&gt; πŸ‘€ At-a-glance
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#at-a-glance
* -&gt; πŸ€” About this comparison
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#about-this-comparison
* -&gt; πŸ§‘β€πŸ’» Example: full-text search
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#example-full-text-search
* -&gt; πŸ¦‰ History Bits
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#history-bits
* -&gt; ✨ Idea spark
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#idea-spark
* -&gt; πŸ—£οΈ Community feedback
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#community-feedback
* -&gt; πŸš€ What’s next?
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#whats-next
* -&gt; πŸ—£οΈ Call to action
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#call-to-action
* -&gt; πŸ”— References
* -&gt; https://www.paulox.net/2025/10/06/django-orm-comparison/#references

*TODO: Analyze why Leo's ~ key handling ~ gets confused - Done?*
</t>
</tnodes>
</leo_file>

Reply via email to