> I made a change in commit b3987a0 to remove the extra stretch around
> some characters in URL's but to allow ragged right formatting within
> URL's. It will break anywhere allowed within a URL no matter how
> much space is left on the line. This produces acceptable results
> (IMHO) for the in
On 3/3/19, Gavin Smith wrote:
> I went looking for past emails about the reasoning behind the choices
> of escape char but found nothing. Did you look into this when you
> wrote texindex?
Karl wanted the escape character to change for index files:
http://lists.gnu.org/archive/html/bug-texinfo/20
On 3/3/19, arn...@skeeve.com wrote:
> If that's the case, then texindex could also special case stuff like
>
> \entry {espresso makers, see coffee makers}{23}{espresso makers, see
> coffee
> makers}
>
> as input and and turn it into
>
> \entry {espresso makers, see coffee makers}{}
>
On 3/3/19, arn...@skeeve.com wrote:
> A few questions.
>
> 1. texindex.awk has provision for both \ and @ to be the command character
> (\entry vs. @entry). Do we still need that? Or will it always be backslash?
I think it could change to @ at some point. The toc and aux files do
use @ as the esc
Hi.
> Maybe it will just have to be accepted that out-of-date versions of
> texindex shouldn't be used with multi-level index entries, otherwise
> the index will appear somewhat mangled.
I think we just have to say that.
> Implemented as @subentry in git commit 372cfab.
>
> A test file is attach
On Tue, Jul 24, 2018 at 10:28:59AM +0200, Werner LEMBERG wrote:
> > I was thinking something like \hfil\allowbreak\hskip 0pt plus -1fil
> > to allow a break at particular characters wherever they occur in the
> > line with the rest of the line being filled up with empty space, but
> > this probably
