1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
|
%global _empty_manifest_terminate_build 0
Name: python-plover-startup-py
Version: 0.2.0
Release: 1
Summary: Quick and dirty plugin to run something when Plover starts.
License: GNU General Public License v3 or later (GPLv3+)
URL: https://github.com/user202729/plover-startup-py
Source0: https://mirrors.aliyun.com/pypi/web/packages/b3/64/e5c9dd4af40b63c9ce26faf1ac403431a62022511394fe4ef63abfc9e461/plover_startup_py-0.2.0.tar.gz
BuildArch: noarch
Requires: python3-plover
%description
# plover-startup-py
Quick and dirty plugin to run something when Plover starts.
### About plugin
This plugin should only used for testing purposes. See also:
* [user202729/plover-debugging-console: A IPython debugging console for Plover.](https://github.com/user202729/plover-debugging-console)
* [user202729/plover-run-py: Command plugin for Plover to run an arbitrary Python command.](https://github.com/user202729/plover-run-py)
Disadvantages in comparison to writing an extension plugin:
* Can only be used on a single machine.
However, it should not be hard to convert a configuration file into an extension plugin to be distributed.
Advantages over writing an extension plugin:
* For testing purposes, the user-provided code might have some bug/errors.
While using a normal extension plugin might make Plover nonfunctional (for example if `stop()` raises
an error, Plover quit will be interrupted), this module guarantees that Plover is never interrupted.
* Has a reload command, which is faster than restarting Plover.
* Some convenience functions to make hacks easier to achieve.
### Installation
The package can be installed from pip or GitHub.
### Configuration
You need to create a file named `plover_startup_py_config.py` in Plover's configuration folder
(see https://plover.readthedocs.io/en/latest/api/oslayer_config.html#plover.oslayer.config.CONFIG_DIR
for where it is exactly)
The file may define (and register) functions `start` and `stop`:
```python
@register_start
def start():
pass
@register_stop
def stop():
pass
```
They will be called when the plugin starts/stops (which is normally when Plover starts/exits)
The engine can be accessed as the global variable `engine`, and there are more convenience functions,
search for "convenience functions" in the source code for more details
(and to read their documentation).
The last line in `load_file()` function in `plover_startup_py/__init__.py` file
have the complete list of global variables passed to the configuration file.
### Usage
Go to "Plugins" tab of Plover configuration, enable the plugin named "plover_startup_py".
To view the full traceback/error messages, you may need to invoke Plover with `--log-level debug`.
There's also an additional command `{plover:plover_startup_py_reload}` for reloading the module.
%package -n python3-plover-startup-py
Summary: Quick and dirty plugin to run something when Plover starts.
Provides: python-plover-startup-py
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-plover-startup-py
# plover-startup-py
Quick and dirty plugin to run something when Plover starts.
### About plugin
This plugin should only used for testing purposes. See also:
* [user202729/plover-debugging-console: A IPython debugging console for Plover.](https://github.com/user202729/plover-debugging-console)
* [user202729/plover-run-py: Command plugin for Plover to run an arbitrary Python command.](https://github.com/user202729/plover-run-py)
Disadvantages in comparison to writing an extension plugin:
* Can only be used on a single machine.
However, it should not be hard to convert a configuration file into an extension plugin to be distributed.
Advantages over writing an extension plugin:
* For testing purposes, the user-provided code might have some bug/errors.
While using a normal extension plugin might make Plover nonfunctional (for example if `stop()` raises
an error, Plover quit will be interrupted), this module guarantees that Plover is never interrupted.
* Has a reload command, which is faster than restarting Plover.
* Some convenience functions to make hacks easier to achieve.
### Installation
The package can be installed from pip or GitHub.
### Configuration
You need to create a file named `plover_startup_py_config.py` in Plover's configuration folder
(see https://plover.readthedocs.io/en/latest/api/oslayer_config.html#plover.oslayer.config.CONFIG_DIR
for where it is exactly)
The file may define (and register) functions `start` and `stop`:
```python
@register_start
def start():
pass
@register_stop
def stop():
pass
```
They will be called when the plugin starts/stops (which is normally when Plover starts/exits)
The engine can be accessed as the global variable `engine`, and there are more convenience functions,
search for "convenience functions" in the source code for more details
(and to read their documentation).
The last line in `load_file()` function in `plover_startup_py/__init__.py` file
have the complete list of global variables passed to the configuration file.
### Usage
Go to "Plugins" tab of Plover configuration, enable the plugin named "plover_startup_py".
To view the full traceback/error messages, you may need to invoke Plover with `--log-level debug`.
There's also an additional command `{plover:plover_startup_py_reload}` for reloading the module.
%package help
Summary: Development documents and examples for plover-startup-py
Provides: python3-plover-startup-py-doc
%description help
# plover-startup-py
Quick and dirty plugin to run something when Plover starts.
### About plugin
This plugin should only used for testing purposes. See also:
* [user202729/plover-debugging-console: A IPython debugging console for Plover.](https://github.com/user202729/plover-debugging-console)
* [user202729/plover-run-py: Command plugin for Plover to run an arbitrary Python command.](https://github.com/user202729/plover-run-py)
Disadvantages in comparison to writing an extension plugin:
* Can only be used on a single machine.
However, it should not be hard to convert a configuration file into an extension plugin to be distributed.
Advantages over writing an extension plugin:
* For testing purposes, the user-provided code might have some bug/errors.
While using a normal extension plugin might make Plover nonfunctional (for example if `stop()` raises
an error, Plover quit will be interrupted), this module guarantees that Plover is never interrupted.
* Has a reload command, which is faster than restarting Plover.
* Some convenience functions to make hacks easier to achieve.
### Installation
The package can be installed from pip or GitHub.
### Configuration
You need to create a file named `plover_startup_py_config.py` in Plover's configuration folder
(see https://plover.readthedocs.io/en/latest/api/oslayer_config.html#plover.oslayer.config.CONFIG_DIR
for where it is exactly)
The file may define (and register) functions `start` and `stop`:
```python
@register_start
def start():
pass
@register_stop
def stop():
pass
```
They will be called when the plugin starts/stops (which is normally when Plover starts/exits)
The engine can be accessed as the global variable `engine`, and there are more convenience functions,
search for "convenience functions" in the source code for more details
(and to read their documentation).
The last line in `load_file()` function in `plover_startup_py/__init__.py` file
have the complete list of global variables passed to the configuration file.
### Usage
Go to "Plugins" tab of Plover configuration, enable the plugin named "plover_startup_py".
To view the full traceback/error messages, you may need to invoke Plover with `--log-level debug`.
There's also an additional command `{plover:plover_startup_py_reload}` for reloading the module.
%prep
%autosetup -n plover_startup_py-0.2.0
%build
%py3_build
%install
%py3_install
install -d -m755 %{buildroot}/%{_pkgdocdir}
if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
pushd %{buildroot}
if [ -d usr/lib ]; then
find usr/lib -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
if [ -d usr/lib64 ]; then
find usr/lib64 -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
if [ -d usr/bin ]; then
find usr/bin -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
if [ -d usr/sbin ]; then
find usr/sbin -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
touch doclist.lst
if [ -d usr/share/man ]; then
find usr/share/man -type f -printf "\"/%h/%f.gz\"\n" >> doclist.lst
fi
popd
mv %{buildroot}/filelist.lst .
mv %{buildroot}/doclist.lst .
%files -n python3-plover-startup-py -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Tue Jun 20 2023 Python_Bot <Python_Bot@openeuler.org> - 0.2.0-1
- Package Spec generated
|
