yatex
view docs/qanda.eng @ 54:2d45e43fb35f
Full support of English documents
| author | yuuji |
|---|---|
| date | Mon, 24 Apr 1995 14:42:53 +0000 |
| parents | |
| children | a9653fbd1c1c |
line source
1 %%
2 %% Q and A on YaTeX
3 %%
4 %% C-u C-x $ shows only questions. C-x $ displays the questions.
5 %%
7 [Installation]
8 *Installing the manual
9 Copy yatexe to the info directory where your Emacs is installed, and
10 add the next line to the dir file of the same directory.
12 * YaTeX: (yatexj). Yet Another tex-mode for Emacs. (Japanese).
14 (After that, M-x info [RET] m yatex [RET] will give you Wild Bird's
15 manual. Hitting ? will show how to use info)
17 *I ain't got the privilege to write in the Info directory...
19 Get yourself made root. If you can't, have them install mule2 and
20 add
22 (setq Info-default-directory-list
23 (cons "YOUR INFO DIRECTORY"
24 Info-default-directory-list))
26 to your ~/.emacs. Now your personal files will be added to the menu
27 when you invoke info. mule1 will not release memories, so processes
28 will pile up and be heavier on the system compared to mule2. Nemacs
29 has already become obsolete by the developers, so no further comments
30 for usage of Nemacs. Get yourself mule2 with flying colors :-)
32 *Emacs can't find the help file.
34 The help file is set to be placed in $EMACS/etc/ for Nemacs, Mule1
35 and $EMACS/site-lisp/ for Mule2. If you don't have the privilege to
36 put them in a public location, copy it to your home directory and
37 set YaTeX-help-file to that file name.
39 *I can't read info on Nemacs
41 The info file was formatted on Mule, so it can't be read correctly on
42 Nemacs (or Demacs based on Nemacs) because the internal Japanese
43 processing is different. Read it on Mule. Use the Emacs-Lisp
44 package in texinfo-3.1.tar.gz to format the Texinfo file.
47 [Operations]
48 *I accidentally learned in a wrong LaTeX command.
50 There should be a line with the wrong command in the .yatexrc file
51 in you home or current directory. Erase that line, do M-x
52 eval-current-buffer and save the results with C-x C-s.
54 *I can't comment out the region.
56 Probably the point is on a line withe \begin{} or \end{}. Go up or
57 down a line and do C-c >.
59 *I was asked for a parent file when typesetting, and answered the wrong file.
61 Re-read the child file with C-x C-v RET or re-type the parent file
62 with C-u C-c ^.
64 *The typeset buffer is not shown when I get a typeset buffer on Demacs.
66 This happens on Demacs 1.2.0, when the child process returns an
67 error level of 1 or more. If you are calling jlatex from a batch
68 file, call a dummy command that always returns errorlevel 0 at the
69 end.
71 *How can I enter "\underline{\makebox[4em][l]{x y}{\tt z}}" more easily?
73 Recursive completion can be used for inputting arguments in the
74 mini-buffer of a section type completion. Following is an example
75 showing the command in question.
77 PROMPT KEYs ENTERED
78 C-c s und SPC RET
79 \underline{???}: C-c s makeb SPC RET
80 Width: 4em RET
81 makebox position (`lr'): - l RET
82 \makebox{???}: x y RET
83 \underline{???}: \makebox[4em][l]{x y} C-c l tt RET
84 \underline{???}: \makebox[4em][l]{x y}{\tt } z RET
86 *How can I kill \footnote{} from \footnote{HOGE}
88 Put the point to \footnote and do C-c k. This will kill the
89 \footnote{}. If you want to kill the whole thing including HOGE, do
90 C-u C-c k.
92 *I want to make HONYARA into a footnote.
94 Mark HONYARA and do C-c S footnote RET. (S in uppercase)
96 *I want to make the verbatim environment I have now into verbatim*.
98 Do C-c c on the line with \begin{verbatim} or \end{verbatim}.
100 *I want to enclose a region with \verb.
102 \verb isn't a maketitle-type, so there aren't any quick commands.
103 But you can use C-c $ to do the same thing.
105 WHAT YOU NEED to make \verb
106 \verbWHAT YOU NEED to make \verb (insert \verb)
107 ^(C-@) (mark W)
108 \verbWHAT YOU NEED to make \verb
109 ^C-c $ (move point to end enclose
110 with $)
111 \verb$WHAT YOU NEED$ to make \verb (done!)
113 *I want to have commands defined on a upper level file to be read in
114 when doing a typeset-region on a child file.
116 When you are editing child files broken into sections and some
117 macros to be used are defined in upper level files, you'll need them
118 to do typeset-region. The macros needed will be copied to the
119 temporary file if you add %#REQUIRE to the end of the macro's
120 definition.
122 Say you had a grand-child file
123 +-- main.tex --+ +---- sub.tex ----+ +-- subsub.tex --+
124 | : | |%#jlatex main | |%#jlatex main |
125 |\include{sub} | |\include{macros} | |..... |
126 | : |<-| : |<-|%#BEGIN |
127 | : | | : | |TEXT YOU WANT |
128 | : | +-----------------+ |TYPESET IS |
129 +--------------+ ^ |HERE |
130 +-- macros.tex ---+ |%#END |
131 |\def\foo{bar} | |: |
132 |\def\hoge{hero} | +----------------+
133 +-----------------+
135 In this case you change the \include{macros} line in sub.tex to
137 \include{macros} %#REQUIRE
139 and add to subsub.tex
141 %#REQUIRE \include{macros}
143 If %#REQUIRE is at the top of the line, the following will be copied
144 to the temporary file. So, macros.tex will be included only once
145 whether you are typesetting all the files, or doing a typeset-region
146 on sub.tex or subsub.tex.
148 *I want to reuse ARGUMENTS I used in the last \foo{ARGUMENTS}
150 Use the gmhist package. YaTeX works fine with gmhist. When you are
151 asked \foo{???}: in the mini-buffer, hitting M-p (ESC p) will get
152 you a history of what you have inputted in reverse. M-n will go
153 forward in the history. This input history can be used for
154 begin-type completion, section-type completion, evoking the
155 previewer, and print out commands.
157 gmhist can be found at many Emacs-Lisp archive sights. For example,
158 ftp.ae.keio.ac.jp:pub/emacs-lisp/util/gmhist.tar.gz
160 *ref<->label jump doesn't work.
162 C-c g will start a forward search of ref/label. C-u C-c g will
163 start a backward search. If you want to continue searching for
164 \ref, hit C-s (C-r) twice and use the repeated search feature of the
165 incremental search. If the point to jump is in another file, that
166 file must be already opened. YaTeX-display-hierarchy (C-c d) can be
167 used to open all files at once.
169 *I get a % at the end of the line when I do a fill-paragraph or auto-fill.
171 NTT-jTeX will add an unnecessary space in the print out image if the
172 japanese paragraph is written with an indent. To avoid this, you
173 need to put a % at the end of the line. YaTeX will automatically
174 put a % so you can input indented text for NTT-jTeX. But there may
175 be a bug in the routine so please report if you find any %s otherwise
176 than at the end of a line.
178 *Isn't the indentation too deep in itemize environments?
180 Think so too? An alias Mr. K thought this was better and he's
181 the only one delighted hitting the TAB key. Wasn't my idea! (still
182 have a bit of a grudge) If you also think it's too deep, hit TAB at
183 the end of the line with \begin{itemize} within the environment.
184 Now it's too shallow? Umm... time for me to take a break.
187 [About Mule2]
188 *Equations are too dark to read when I use Mule2+hilit19.
190 The default coloring of hilit19.el is too dark. Try putting the
191 next code in ~/.emacs or yatexhks.el.
193 (if (and (featurep 'hilit19) (eq hilit-background-mode 'dark))
194 (hilit-translate
195 string 'mediumspringgreen
196 formula 'khaki
197 label 'yellow-underlined))
199 *Can't I use font-lock?
201 The document says, "pattern must be specified within a line". So it
202 seems you can't chose a pattern like from \begin to \end that laps
203 more than one line. But on the other hand, multiple line comments
204 in C seems to work fine... So what's the real story? Anybody know
205 the answer? If so, teach me, or try sending a fan letter to our
206 font-lock investigator-in-depress Taguchi (tagu@ae.keio.ac.jp)
208 *It's sooo slow when I click YaTeX on the menu bar.
210 I don't know why. Probably a problem with Emacs-19. You'll just
211 have to bear with it. It won't be so slow the second time.
212 Anyway, you probably won't use the menu at all, do you?
214 [Customization]
215 *I don't use C-c b i much, so it would be better if I can start
216 completion after hitting C-c b.
218 Put (setq YaTeX-no-begend-shortcut t) in your ~/.emacs.
220 *An open parenthesis always get entered in pairs.
222 This should be better, once you get used to it. If you still don't
223 like it, turn on modify-mode using C-c w m. Setting
224 YaTeX-close-paren-always to nil will give this feature from the start.
226 *Funny things happen when I hit ;.
228 YaTeX think you are in math mode and evokes math-mode-image
229 completion. If you are writing a equation that TeX will not give an
230 error and YaTeX mistakes what mode you are in, report it back to the
231 author. For mistaken judgements or if you want to enter a literal
232 ;, hit ; twice. C-u ; to use ; as a image-completion prefix.
234 *I want YaTeX to enter the option arguments for a newenvironment.
236 Read yatexadd.doc. If that's not enough, read yatexgen.doc and try
237 M-x YaTeX-generate.
239 *I first defined \foo as a macro taking 3 arguments. Later I changed it
240 to take 4 arguments, but the section-type completion will ask me for
241 only 3 arguments.
243 Use C-u 4 C-c s and tell it will take 4 arguments. You can change
244 the number of arguments anytime you want.
246 *I made a argument-type addin function, but can't do completion after
247 the first two arguments.
249 If you made a addin function like \foo{x}{y}{z} that takes 3
250 arguments, then you need to learn in the dictionary that \foo will
251 take 3 arguments. This can be done by C-u 3 C-c s foo. You only
252 need to do it once.
254 *My addin functions are overwritten by yatexadd.
256 Formally, all private functions were written in your own yatexadd.el.
257 Now, all private functions are put in yatexhks.el. yatexhks.el will
258 be read in at the end of YaTeX's initialization, so you can overwrite
259 definitions in yatexadd.el.
261 [ETC]
262 *Mailing lists?
264 A question, so an answer. The mailing list for YaTeX(Wild Bird) and
265 it's implementation to Vz, Raicho (by katsura@prc.tsukuba.ac.jp) is
266 "fj Wild Bird Society". Send a mail like
268 To: yatex-control@harvest.jaist.ac.jp
269 Subject: append
270 -----
271 Hi! See any birds fly by?
273 and you're in. The text will be used as your profile. (you can
274 change it later) Once you're in, you'll get a reply with lists of
275 commands used in the mailing list. Join along and help adding new
276 feathers to Wild Bird. BTW, if you haven't guessed it yet, yes,
277 this mailing list is in Japanese. But give us a try anyway. You're
278 always welcome.
280 *Help, help HELP!!
282 Ways of getting answers in fastest order.
284 *Look for someone near you who knows what's he/she's doing.
285 *Post a question to the mailing list.
286 *Send mail to yuuji@ae.keio.ac.jp
288 take a pick.
290 *Picking a question in this file with C-u C-x $ and hitting C-x $ takes
291 me to a weird world.
293 You too? Try marking the question before C-x $ and to C-x C-x to
294 take you back to it. (mule2 doesn't seem to have the same problem)
297 Local Variables:
298 mode: indented-text
299 fill-column: 72
300 fill-prefix: " "
301 End: