LaTeX.org

So, with some time to spare today for this problem, I decided to try rewriting the macro from scratch (instead of adapting the existing code) and was able to solve my problem. Below is a MWE which shows the macro working as expected. The new version of the macro doesn't contain quite so many ...

I'm writing a macro which is designed to allow the user to fill a box in a recursive fashion. I.e. if the box is empty, then the macro simply populates the box with the user designated material. If the box is not empty, then the new material is added to the old material on a new line (with alignment ...

That worked perfectly.

This environment (and the xesearch package it's based on) is something of a black box for me. I use it, but I don't know exactly what it's doing or why it works (during the actual counting process). I suppose I should take a better look at it, but don't really have the time ...

In the MWE below I've defined an environment that counts the number of words inside based on this question over on StackExchange . I'd like to modify it further to allow me to exclude blocks of text from the count (by defining \exclude appropriately). Does anyone have any suggestions on how to best ...

That works great. Thanks much.

I'm sure I'll now find other uses for this method of defining several unique variables too.

I have a personalized class file in which I've defined the following environment:

\newcounter{words}
\newenvironment{counted}{%
\noindent\hrulefill\par
\marginpar{\footnotesize\textit{Begin counting words}}
\setcounter{words}{0}
\SearchList!{wordcount}{\stepcounter{words}}
{a?,b?,c?,d?,e?,f ...

Got an answer over on stackexchange. Turns out that the \@ifnextchar, within \ie was checking \punctuationcheck rather than the actual text. In order for it to look back at the actual text, I had to move \punctuationcheck inside the code tokens so that there was nothing after the three arguments to ...

When I compile the below MWE the first \@ifnextchar, always evaluates to false, which is clearly wrong in the last case. However, the second one (within \punctuationcheck ) works just fine. Why would the same conditional evaluate to False and then True?

\documentclass{article}

\makeatletter ...

I have some photos that I'm including in a book I'm writing which I want to display as full page images (on custom sized pages). I'd like the following parameters to be applied to the way the image displays:

If the photo is landscape oriented, then it, and its caption, should be rotated 90 ...

That does fix it. Thanks for the help.

I've purposely avoided the \arraybackslash in the new column types because this table is actually defined in a command and then used over and over again, potentially with multi-line arguments going into some of the cells which use '\\' to mark the line breaks.