headers
Joost Kremers | 2 Jun 2008 11:49

Re: Fold citep

On Sat, May 31, 2008 at 06:58:45PM +0200, Ralf Angeli wrote:
> > sorry, my question was confusing. what i meant to say was: what happens
> > if the optional argument isn't there, and the user hasn't supplied an
> > *alternative string*?
> 
> Then the placeholder would be replaced by an empty string, I guess.

so it's up to the user to make sure that folding doesn't actually make a
LaTeX command disappear altogether? (if i specify "[1]" as replacement
string for \item, and i use \item without any argument, it disappears
completely.)

> > mmm... perhaps i'm not understanding you correctly... isn't this what you
> > get when you supply "*" as the alternative string? i.e. if you specify
> > "[1:*]" as the replacement string?
> 
> This would result in "*" for "\item", but "foo" for "\item[foo]".  In
> order to get "foo:" for "\item[foo]" one would need to supply "[1:*]:"
> but this would result in "*:" for "\item".

oh, sorry, i hadn't seen the second colon in your example...

i'm not sure whether this is really a problem. personally, i wouldn't
supply such a colon in the replacement string if the command i'm folding
doesn't actually produce that colon. the reason being that as a general
rule, folding makes the text in the editor appear more like the resulting
dvi/pdf text.

--

-- 
Joost Kremers, PhD
(Continue reading)

Permalink | Reply | 2 comments |
headers
Ralf Angeli | 2 Jun 2008 18:40

Re: Fold citep

* Joost Kremers (2008-06-02) writes:

> On Sat, May 31, 2008 at 06:58:45PM +0200, Ralf Angeli wrote:
>> > sorry, my question was confusing. what i meant to say was: what happens
>> > if the optional argument isn't there, and the user hasn't supplied an
>> > *alternative string*?
>> 
>> Then the placeholder would be replaced by an empty string, I guess.
>
> so it's up to the user to make sure that folding doesn't actually make a
> LaTeX command disappear altogether?

Yes.  One could add a safeguard by displaying an ellipsis if the
display string becomes empty.

--

-- 
Ralf
Permalink | Reply | 1 comment |
headers
Ed C. | 5 Jun 2008 01:41

Exporting manual hyphenation instances to ispell or aspell.

I have many .tex files in a language with no suitable dictionary and I 
want to start constructing one by making word lists from files where I 
have manually inserted \- (discretionary hyphens) between syllables all 
over the place in documents with Overfull box warnings in order to get 
justification in my pdfs.
I am using emacs, auctex, and miktex on w2000 and have only ispell-win32 
to work with. Has any of you tried to do something like this before? Is 
there a web site with a newbie friendly recipe for assemlbling the 
needed files on w32 (lang.dat, lang.dic, lang.aff, lang.hash .... are 
there others?)
It seems like elisp might be an appropriate tool for solving my problem.

Thanks,

Ed
Permalink | Reply | 0 comments |
headers
Ed C. | 6 Jun 2008 06:26

Exporting manual hyphenation instances to ispell or aspell. (second attempt)

I have many .tex files in a language with no suitable dictionary and I 
want to start constructing one by making word lists from files where I 
have manually inserted \- (discretionary hyphens) between syllables all 
over the place in documents with Overfull box warnings in order to get 
justification in my pdfs.
I am using emacs, auctex, and miktex on w2000 and have only ispell-win32 
to work with. Has any of you tried to do something like this before? Is 
there a web site with a newbie friendly recipe for assemlbling the 
needed files on w32 (lang.dat, lang.dic, lang.aff, lang.hash .... are 
there others?)
It seems like elisp might be an appropriate tool for solving my problem.

Thanks,

Ed
Permalink | Reply | 0 comments |
headers
Sebastian P. Luque | 6 Jun 2008 06:10
Picon
Gravatar

botched tool bar icons

Hi,

Using the following minimal file (~/tmp/auctex_toolbar_bug.tex):

---<---------------cut here---------------start-------------->---
\documentclass[10pt]{beamer}

\title{What?}

\author{Who?}

\begin{document}

\begin{frame}
  \titlepage
\end{frame}

\section{Introduction}

\begin{frame}
  \frametitle{Section A}

\end{frame}

\end{document}

%%% Local Variables:
%%% TeX-PDF-mode: t
%%% End:
---<---------------cut here---------------end---------------->---
(Continue reading)

Permalink | Reply | 0 comments |
headers
Angelo Graziosi | 6 Jun 2008 17:28
Picon

Strange behaviour of toolbar icon (Emacs/AUCTeX)

For the sake of completeness, I want to flag the following facts that
happen on GNU/Linux Kubuntu 8.04 with current
Emacs-23.0.60-trunk+GTK+AUCTeX-11.85 (or AUCTeX-CVS).

Now, If I start with an empty .emacs.desktop, Emacs loads only the
'scratch' and 'Messages' buffers, and the dired icon on the toolbar
shows up as in 'cut_ico.png' image attached, i.e. it looks with a little
cut in one edge.

If now I load a '.tex' file, the Emacs toolbar is changed with
AUCTeX toolbar ('auc_ico.png' images).

After this, switching to 'scratch' buffer or 'Messages' or loading 
another file which uses Emacs toolbar, then the dired icon looks as in 
'ok_ico.png' image, i.e. it seems OK, without the little cut.

If I start Emacs with 'emacs -q' the dired icon is shown always
with a little cut, as in 'cut_ico.png' image, whatever file is loaded.

Cheers,
    Angelo.
Attachment (ico_images.tar.bz2): application/octet-stream, 9 KiB
Permalink | Reply | 0 comments |
headers
Sebastian P. Luque | 6 Jun 2008 06:10
Picon
Gravatar

botched tool bar icons

Hi,

Using the following minimal file (~/tmp/auctex_toolbar_bug.tex):

---<---------------cut here---------------start-------------->---
\documentclass[10pt]{beamer}

\title{What?}

\author{Who?}

\begin{document}

\begin{frame}
  \titlepage
\end{frame}

\section{Introduction}

\begin{frame}
  \frametitle{Section A}

\end{frame}

\end{document}

%%% Local Variables:
%%% TeX-PDF-mode: t
%%% End:
---<---------------cut here---------------end---------------->---
(Continue reading)

Permalink | Reply | 3 comments |
headers
gerald.jean | 6 Jun 2008 20:06
Picon

Finding "unresolved references" in a large document.


Hello there,

I find very handy the ability of AucTeX of finding duplicate labels in a
multi-file document.  I was wondering if there is a way to do something
similar for "unresolved references"?  It is a pain to locate them in a
large multi-file document.

Thanks,

Gérald Jean
Conseiller senior en statistiques, Actuariat
télephone            : (418) 835-4900 poste (7639)
télecopieur          : (418) 835-6657
courrier électronique: gerald.jean <at> dgag.ca

"There are two rules for ultimate success in life.
1) Never tell everything you know"
Permalink | Reply | 1 comment |
headers
Sebastian P. Luque | 6 Jun 2008 22:30
Picon
Gravatar

Re: botched tool bar icons

On Thu, 05 Jun 2008 23:10:56 -0500,
"Sebastian P. Luque" <spluque <at> gmail.com> wrote:

[...]

> This is with GNU Emacs 23.0.60.1 (x86_64-pc-linux-gnu, GTK+ Version
> 2.12.9) of 2008-05-30 on elegiac, modified by Debian, and AUCTeX
> 11.83-7.1 (Debian sid package).

It must have been a transitory bug with the previous Emacs snapshot,
since today's snapshot version: GNU Emacs 23.0.60.1
(x86_64-pc-linux-gnu, GTK+ Version 2.12.10) of 2008-06-06 on elegiac,
modified by Debian, doesn't display this problem anymore.  Sorry for the
unnecessary report.

--

-- 
Seb
Permalink | Reply | 2 comments |
headers
Ralf Angeli | 7 Jun 2008 10:25

Re: Finding "unresolved references" in a large document.

* gerald jean (2008-06-06) writes:

> I find very handy the ability of AucTeX of finding duplicate labels in a
> multi-file document.

This is not an AUCTeX feature but one of RefTeX.

> I was wondering if there is a way to do something
> similar for "unresolved references"?  It is a pain to locate them in a
> large multi-file document.

The processor will tell you those unresolved references during
compilation of the document.  You can jump to them just like to an error
with `C-c `' or `M-g n' if you enable debugging of warnings with `C-c
C-t C-w' or via the `TeXing options' menu.

--

-- 
Ralf
Permalink | Reply | 0 comments |

Gmane