Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No way to all-caps just the beginning of a word #837

Closed
arxanas opened this issue Nov 14, 2017 · 6 comments
Closed

No way to all-caps just the beginning of a word #837

arxanas opened this issue Nov 14, 2017 · 6 comments

Comments

@arxanas
Copy link

arxanas commented Nov 14, 2017

Classification: Bug

Reproducibility: Always

Summary

Suppose you have the dictionary

"PEUD": "pid",
"TPAOEUL": "file",
"KPA*TS": "{*<}",
"H*PB": "{^-^}",
"TK-LS": "{^^}",

and you try to write PID-file:

PEUD/KPA*TS/H*PB/TK-LS/TPAOEUL

This actually produces

PID-FILE

Instead of

PID-file

In general there doesn't seem to be a way to make capitalizing the previous part of the word not affect the next part of the word.

Version

Plover version 4.0.0.dev5 @ ff51971
Installed via: source

Configuration

ProductName:    Mac OS X
ProductVersion: 10.12.6
BuildVersion:   16G29
@benoit-pierre
Copy link
Member

This is an intentional change from previous versions, the question is do we want something like this to work:

    def test_retro_upper7(self):
        r'''
        'TEFT': 'test',
        "W-G": "{^ing with}",
        'RUP': '{*<}',

        TEFT/RUP/W-G  " TESTING with"
        '''

?

@arxanas
Copy link
Author

arxanas commented Nov 21, 2017

@benoit-pierre: What's the recommended way of writing a word like "PID-file", then? I generally use retroactive capitalization instead of preemptive capitalization, and it doesn't seem like there's a good way to accomplish this anymore, since I can't even use TK-LS to cancel the capitalization.

@TheaMorin
Copy link
Member

I think the example in the OP is more realistic than the "test^ing with" issue. I'd probably still expect
"TESTing with" due to the location of RUP.

@arxanas
Copy link
Author

arxanas commented Nov 21, 2017

This also appears to be manifesting when I'm coding. I tried to write this

  return SomeEnum::SOME_VALUE;
}

public

but got

  return SomeEnum::SOME_VALUE;
}

PUBLIC

where I typed

SOM/RUND/VAOUL/KPA*TS # SOME_VALUE
STPH*FPLT  # ;
STPH*B/STPH*B  # down-arrow a few times
R*R/R*R
PLIK

where R*R is defined to be {MODE:RESET}{^}\n{^}. There's even an explicit mode-reset in there. I also tried issuing explicit mode-resets with my KLAO*ER stroke.

What exactly am I supposed to do at this point? Go back up to the previous point in the code and delete everything I just typed and then try again, this time without using capitalize-last-word? Give up and restart Plover? It's not even as if I can reset the current mode and continue at the current position.

@TheaMorin
Copy link
Member

Fixed by #865

@gdwaynewarner
Copy link

My Phoenix Theory Medical dictionary has P*-EUD for "PID." So if I wanted "PID-file," I would just stroke that first outline, the hyphen stroke (P-F), and, of course, follow it up with my stroke for "file."

Looks like you're working way too hard for an outline that is actually in steno-order! :o)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants