TSE: What are the most frequently used key actions on Microsoft Windows editing applications?

[knud van eeden]

Hello,

FYI:

> What are the most frequently used key actions on Microsoft Windows editing applications?

AI Overview

The most frequently used keyboard actions (shortcuts) for editing in Microsoft Windows applications are designed to minimize mouse movement, with 

Ctrl+C (Copy), Ctrl+V (Paste), Ctrl+Z (Undo), and Ctrl+S (Save) being the most essential across almost all software. These actions are fundamental in text editors, image editors, and Office applications. 

Medium +2

Here are the top, most frequently used editing key actions, ranked by ubiquity and frequency of use:

Core Editing & Document Action

• Ctrl + V (Paste): Paste the last item from the clipboard.
• Ctrl + C (Copy): Copy selected items/text.
• Ctrl + Z (Undo): Undo the previous action.
• Ctrl + X (Cut): Cut selected items/text.
• Ctrl + S (Save): Save the current document or file.
• Ctrl + A (Select All): Select all text or items in a document/window.
• Ctrl + Y (Redo): Redo the last undone action. 
  Microsoft Support +3

with friendly greetings

Knud van Eeden

[S.E. Mitchell]

I think we've discussed this topic (CUA keys in tse.ui) enough.

I have no plans to make tse.ui CUA compliant at this time.

I _might_ add ctrl v for paste(), ctrl c for copytowinclip(), and ctrl a for markall() (ascii chart is on the menus) in a future version.

But I do not plan on changing ctrl z, ctrl x, ctrl y, and ctrl a at the current time.

If users want the so-called "common Windows keys" they should install the win.ui.

The setup program even defaults to that, so new users (if there ever are any) will get the common Windows keys.

But sending me the same thing over and over does not change my mind - if anything it makes me dig in my heels :)

[knud van eeden]

In general what users make drop a product is not what it can do in general,

but what it can NOT do (no check, no check, no check, ..., drop, different (text editor) product), like not implementing the most used 

keys in a text editor implemented as a Microsoft Windows application.

I hope I do not have to go into more precise details about what is NOT implemented and what it effect was

in the course of the years ;-) 

--

---
You received this message because you are subscribed to the Google Groups "SemWare TSE Pro text editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email to semware+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/semware/CA%2BgEvka1WsPZhqy%2BULYGzf0hKohL8WSp8tSBtBDXGmjauBGJ8Q%40mail.gmail.com.

[Claus Futtrup]

>different (text editor) product

That's rather optimistic. In fact a (good) text editor becomes a habit and finding a replacement is difficult because most of the alternatives cannot do what you want how you want (but some might be capable with significant fiddling with configuration).

/Claus

To view this discussion visit https://groups.google.com/d/msgid/semware/1707709272.1111612.1774714180656%40mail.yahoo.com.

[knud van eeden]

Agreed for the non-educated users ;-)

The educated users know what to keep and what not.

with friendly greetings

Knud van Eeden

To view this discussion visit https://groups.google.com/d/msgid/semware/027d2317-eeda-4461-8e67-5a365ec3eae4%40gmail.com.

[Henriques18]

Well maybe then you, as an educated user, should use notepad or write your own editor.

Op zaterdag 28 maart 2026 om 19:24:33 UTC+1 schreef knud van eeden:

[knud van eeden]

Good hint for yourself instead. Good luck.

To view this discussion visit https://groups.google.com/d/msgid/semware/a3fb09b1-3bf0-44fa-8891-845328944169n%40googlegroups.com.

[knud van eeden]

I contact you about it in 40 years, when you maybe are finished with that job of writing your editor, if anything finished. Probably not.

[knud van eeden]

On the other hand, if I, as aa really educated user, instead of you thus as a non-educated user, really wanted that,

I could with the help of AI write the framework of any text editor in a few days, even some basic TSE clone.

But I have better things to do.

[Guy Rouillier]

As an aside, if anyone wants to add their own key customization to TSE, an easy way to do this is to use a #include directive in your interface file of choice (tse.ui, win.ui, etc.), and put your customized key definitions in a separate file.  For example, I use tse.ui, and put my customizations in a file called guyr.ui.  How does this help?  When a new TSE version is released, you can simply copy your #include statement from the previous version to the new version, and use sc32 to burn your key customizations into the new version.  If interested, here is the procedure I follow:

(1)  In the supplied UI files, search for "TSE Pull-down Menus".  Put your #include immediately *before* this.  Why? I discovered that when sc32 finds a duplicate definition, it will print "duplicate definition found", but will retain the first definition and keep on going.  So, you want to put your custom key definitions *before* any of the standard definitions.

(2) Now, edit your include file, and put your custom key definitions there. You can also put any of your own procs needed by your custom key definitions in the same file.

(3) Finally, use sc32 to burn your custom key definitions into the editor.  Burn in the top level ui file (tse.ui for me).  The compiler will find the #include statement and automatically include your custom definitions.

Hope this helps.

--

---
You received this message because you are subscribed to the Google Groups "SemWare TSE Pro text editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email to semware+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/semware/CA%2BgEvka1WsPZhqy%2BULYGzf0hKohL8WSp8tSBtBDXGmjauBGJ8Q%40mail.gmail.com.

-- 

Guy Rouillier

[zhong zhao]

The most frequently used key actions on my TSE is <alt z> compress view the current word in all opened files.

//...in ui\tse.ui

//...

proc mCVW()
    string word[255],opstr[4]

    word=GetWord(1)
    if Length(word) == 0 or word=="@" or word=="$"
        return()
    endif
    opstr='wv'
    if (sort_flags & _IGNORE_CASE_) <> 0
        opstr=opstr+'i'
    endif
    opstr=opstr+'a'
    if not lFind(word, opstr)
        Warn(word, " not found.")
    endif
end

//...

<Alt z>                 mCVW(）
//...