aboutsummaryrefslogtreecommitdiffhomepage
path: root/FAQ.md
blob: d72d8062ecc5f45328b62e5239e63149dbefe6ad (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
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
# FAQ

**Q:**
I upgraded to Textadept 7 and the editor displays a strange error message on
startup and/or exits. Also my themes do not seem to work anymore.

**A:**
Textadept 7 introduced API changes and a completely new theme implementation.
Please see the [migration guide][] for more information. It may help to either
delete your old `~/.textadept/` folder or move everything within it somewhere
else before gradually copying those files back to see which of them causes an
error.

[migration guide]: 14_Appendix.html#Textadept.6.to.7

- - -

**Q:**
What is the difference between *textadept* and *textadeptjit*? Which one should
I use?

**A:**
*textadept* uses Lua 5.2 while *textadeptjit* uses [LuaJIT][], which is based on
Lua 5.1. Other than access to the [FFI Library][], *textadeptjit* does not
provide any noteworthy benefits. It used to be the case that *textadeptjit* was
slightly faster when loading large files, but Textadept 6.1 was the last version
that had a noticible difference between the two. *textadept* is recommended.

[LuaJIT]: http://luajit.org
[FFI library]: http://luajit.org/ext_ffi.html

- - -

**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 many distributions since late 2009
while the latest 2012 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 for the GUI version. (A development library for a curses
implementation is required for the terminal version.)

[compiling]: 12_Compiling.html

- - -

**Q:**
I'm trying to compile Textadept from one of the download packages, but get some
obscure errors in the `scintilla/term/`, `gtdialog/`, or `scintillua/`
directories. What happened?

**A:**
Some of the dependencies Textadept downloads are the latest archives in their
respective version control repositories. Occasionally there are compile-time
incompatibilities with these "bleeding-edge" downloads. The solution is to go to
the appropriate repository and download the archive tagged for the version of
Textadept you downloaded.

For example, if you have Textadept 7.1 and cannot build the terminal version due
to a file in the `scintilla/term/` directory, go to [scinterm hg][] and look for
the "for\_textadept\_7.1" tag, click on it, download the [zip][], and replace
the problematic file.

[scinterm hg]: http://foicica.com/hg/scinterm
[zip]: http://foicica.com/hg/scinterm/archive/ea13ae30cfab.zip

- - -

**Q:**
When I open a file in a non-English language, I see a lot of strange characters.

**A:**
Textadept does not detect the file's encoding correctly. You'll need to
[help it][].

[help it]: 04_WorkingWithFiles.html#Encodings

- - -

**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:**
Please see the LuaDoc on [compile and run commands][].

[compile and run commands]: api/_M.html#Compile.and.Run

- - -

**Q:**
The curses version does not support feature _x_ the GUI version does. Is this a
bug?

**A:**
Maybe. Some terminals do not recognize certain key commands like `Shift+Arrow`
for making selections. Linux's virtual terminals (the ones accessible with
`Ctrl+Alt+FunctionKey`) are an example. GNOME Terminal, LXTerminal and XTerm
seem to work fine. rxvt and rxvt-unicode do not work out of the box, but may be
configurable.

Please see the [curses compatibility][] section of the appendix. If the feature
in question is not listed there, it may be a bug. Please [contact][] me with any
bug reports.

[curses compatibility]: 14_Appendix.html#Curses.Compatibility
[contact]: README.html#Contact

- - -

**Q:**
Pressing `^O` in the curses version on Mac OSX does not do anything. Why?

**A:**
For whatever reason, `^O` is discarded by the terminal driver. To enable it, run
`stty discard undef` first. You can put the command in your *~/.bashrc* or
*~/.bash_profile* to make it permanent.

- - -

**Q:**
How can I get the terminal version on Mac OSX to show more than 8 colors?

**A:**
Enable the "Use bright colors for bold text" setting in your Terminal.app
preferences.

- - -

**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.

- - -