Lightweight extension for on-the-fly manipulation to primary selections, especially optimized for Dictionary lookups For support, please report any issues via the homepage link below.
Note: Binary files aren't shown on the web site. To see all files, please download the extension zipfile.
| Version | Status |
|---|---|
| 79 | Unreviewed |
| 78 | Active |
| 77 | Active |
| 76 | Active |
| 75 | Rejected |
| 74 | Active |
| 73 | Rejected |
| 72 | Rejected |
| 71 | Active |
| 70 | Inactive |
| 69 | Inactive |
| 68 | Active |
| 67 | Active |
| 66 | Rejected |
| 65 | Active |
| 64 | Inactive |
| 63 | Inactive |
| 62 | Inactive |
| 61 | Inactive |
| 60 | Inactive |
| 59 | Inactive |
| 58 | Active |
| 57 | Inactive |
| 56 | Inactive |
| 55 | Rejected |
| 54 | Inactive |
| 53 | Inactive |
| 52 | Inactive |
| 51 | Inactive |
| 50 | Rejected |
| 49 | Inactive |
| 48 | Rejected |
| 47 | Active |
| 46 | Inactive |
| 45 | Rejected |
| 44 | Rejected |
| 43 | Rejected |
| 42 | Rejected |
| 41 | Inactive |
| 40 | Rejected |
| 39 | Inactive |
| 38 | Inactive |
| 37 | Rejected |
| 36 | Inactive |
| 35 | Rejected |
| 34 | Rejected |
| 33 | Rejected |
| 32 | Rejected |
| 31 | Inactive |
| 30 | Rejected |
| 29 | Rejected |
| 28 | Active |
| 27 | Active |
| 26 | Rejected |
| 25 | Inactive |
| 24 | Rejected |
| 23 | Inactive |
| 22 | Inactive |
| 21 | Rejected |
| 20 | Rejected |
| 19 | Rejected |
| 18 | Rejected |
| 17 | Rejected |
| 16 | Inactive |
| 15 | Rejected |
| 14 | Inactive |
| 13 | Inactive |
| 12 | Inactive |
| 11 | Inactive |
| 10 | Inactive |
| 9 | Inactive |
| 8 | Inactive |
| 7 | Inactive |
| 6 | Inactive |
| 5 | Inactive |
| 4 | Inactive |
| 3 | Inactive |
| 2 | Inactive |
| 1 | Rejected |
The `LDOCRPY` in line 18 `prefs.js`. Should it still be there? I see that is getting used for `execute()`.
> The `LDOCRPY` in line 18 `prefs.js`. Should it still be there? I see that is getting used for `execute()`. It's used to detect the existence of `ldocr.py`(line 538) and `execute()` if exists (line 585) so that if the file does not exist, the code will not be executed.
I understand. I mean when the package doesn't have that, it shouldn't be there in the first place. Approved this one. Please remove those lines for the next version. Thanks!
> I understand. I mean when the package doesn't have that, it shouldn't be there in the first place. This path is where the script is expected to be installed, and I think a fixed path is a bit more reliable than running an executable under the user's PATH. The code is kept for the convenience of those users who need this functionality and install the file themselves. For other users, these lines are almost zero cost.
It's ok. You can also add the dependency to the description.
Light Dict