blob: 56a13169d57fb374691b80edc9046cd04c14f478 (
plain)
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
|
# FAQ
**Q:**
On Linux I get a `error while loading shared libraries: <lib>: cannot open`
`shared object file: No such file or directory` when trying to run Textadept.
How do I fix it?
**A:**
It is difficult to provide a binary that runs on all Linux platforms since the
library versions installed vary widely from distribution to distribution. For
example, `libpng14` has been available for my Archlinux distribution since late
2009 while the late 2010 Ubuntu still uses `libpng12`. Unfortunately in these
cases, the best idea is to compile Textadept. This process is actually very
simple though. See the [compiling][] page. Only the GTK development libraries
are needed.
If you get a `libpng12` error, try using the `textadept.lpng12` executable
instead of `textadept`.
[compiling]: 12_Compiling.html
- - -
**Q.**
After upgrading to Textadept 5 from Textadept 4, Textadept 5 crashes hard with
no messages. What can I do?
**A:**
You likely have old modules that are not compatible with Textadept 5. Most
offending modules use the `module()` Lua 5.1 function which was removed in Lua
5.2. You can temporarily move your `~/.textadept/` directory elsewhere and
restart Textadept to be sure old modules are causing problems. You can correct
them using the [migration guide][].
[migration guide]: 14_Appendix.html#Textadept.4.to.5
- - -
**Q:**
I downloaded the Linux version, but when I try to compile it, some files are not
found. Where do I get these files?
**A:**
You need to download the source version of the release, not the binary version.
The source version contains all the files necessary for compiling Textadept.
- - -
**Q:**
Autocompletion does not work for my language. Why not?
**A:**
`modules/textadept/key_commands.lua` calls
[`_M.textadept.editing.autocomplete_word()`][] with `'%w_'`, which in [Lua][] is
all ASCII alphanumeric characters and underscores. You can add character ranges
in `'\xXX-\xXX'` or `'\ddd-\ddd'` [format][] (e.g. `'%w_\127-\255'`).
Unfortunately this probably will not work for unicode.
[`_M.textadept.editing.autocomplete_word()`]: api/_M.textadept.editing.html#autocomplete_word
[Lua]: 14_Appendix.html#Lua.Patterns
[Format]: http://www.lua.org/manual/5.2/manual.html#3.1
- - -
**Q:**
When I click the "Compile" or "Run" menu item (or execute the key command),
either nothing happens or the wrong command is executed. How can I tell
Textadept which command to run?
**A:**
Take a look at these [commands][].
[commands]: http://foicica.com/wiki/run-supplemental
- - -
**Q:**
Clicking "Block Comment" (or executing the key command) does nothing. Why?
**A:**
Take a look at these [comments][].
[comments]: http://foicica.com/wiki/comment-supplemental
- - -
**Q:**
Are my Textadept 4.x scripts compatible with Textadept 5.x?
**A:**
No. Lua was updated to 5.2 and there were some API changes. See the [migration
guide][].
[migration guide]: 14_Appendix.html#Textadept.4.to.5
- - -
**Q:**
Why does Textadept remember its window size but not its window position?
**A:**
Your window manager is to blame. Textadept is not responsible for, and should
never attempt to set its window position.
- - -
|
