Reputation
Top tag
Next privilege 250 Rep.
View close votes
Badges
1 11
Newest
 Critic
Impact
~3k people reached

Feb
1
comment How can I centre merged columns with tabulary?
I didn't mean to complain to you. I was trying to thank you for clarifying that it was known that booktabs causes the gaps I was getting.
Feb
1
comment How can I centre merged columns with tabulary?
I've not reviewed the source but I'm convinced nothing is easy in TeX. However, when one is producing a package for public use, extra effort to "get it right" is called for (more than one would put into a single doc). I realize that it was a design choice they made; my point is that it's an extremely poor design choice. They could encourage the disuse of vertical lines, one can get away with that in many small tables that look fine. However there are tables that demand the use of vertical lines, and now one must trade one feature set for another. The option to use both is taken away.
Feb
1
awarded  Critic
Feb
1
comment How to draw two \hline and two vertical line?
+Svend I couldn't disagree more. SOME tables look nice without vertical lines, but there are MANY tables that demand them, and the notion that they should be avoided at all cost is a horrific one that is way too prevalent in the LaTeX community.
Feb
1
comment How can I centre merged columns with tabulary?
I've been going nuts trying to figure out what I'd screwed up so my table's horizontal and vertical lines didn't connect anymore. I'd seen the \toprule etc in this question and thought: "Oh, I should use that. Why shouldn't I make use of other's automated spacing work?" Now I know. Removing vertical lines is a HORRIBLE choice. They could easily have designed it so that it works great if you leave them out, but then also works fine if you leave them in, when they're needed. Instead of extending functionality, they've replaced functionality.
Jan
9
awarded  Self-Learner
Dec
11
revised A symbol for the quotient of two objects
added 242 characters in body
Dec
11
answered A symbol for the quotient of two objects
Nov
17
awarded  Notable Question
Nov
16
answered Cause DeclarePairedDelimiter to switch starred and nonstarred versions
Nov
16
comment Path to External Files in Nested \input
I was having this exact problem, and ended up here. I was disappointed that it seems nothing on this page explains why it's happening. While reading I kept tweaking things, and I think I know what's going on. While compiling the main document, it interprets the relative path from the location of the main tex file. If all projects folders have the same relative path to the common folder, you can write cosmetix.tex to input the other file as if it's in a project file. In my case, this won't work, since I have subprojects. I look forward to trying out import.
Nov
16
comment Cause DeclarePairedDelimiter to switch starred and nonstarred versions
Then I'd better change it or I'll get confused. Ok, I think I see what's happening now. We're defining \RIGHTabs and \abs. The first has a starred version that automatically resizes. The second command checks for stars and optional characters and calls the right version of the first command. OMG, is RIGHT a pun on Wrongly? :-D I can probably work my way through replacing \DeclarePairedDelimiterX\innerp[2]{\langle}{\rangle}{#1,#2} now. (While putting this in my pre file, I realized it would only let me fix about 2/3 of my commands.) This is robust, thanks!
Nov
16
accepted Cause DeclarePairedDelimiter to switch starred and nonstarred versions
Nov
16
comment Cause DeclarePairedDelimiter to switch starred and nonstarred versions
lol. Sometimes I'm not satisfied with the automatic sizing, but it's because it's too small and I override it with larger sizes. I'm guessing RIGHT gets interpreted as \right, but why is it followed with the new command's name #1, and why is there no LEFT?
Nov
16
comment Cause DeclarePairedDelimiter to switch starred and nonstarred versions
I'm trying to guess why it's wrong and if the "better" way handling the optional parameter fixes the wrongness (but my brain doesn't want any more TEX today). I tested it and both versions will accept the option now, though I can't see why. Is there a reason you switched to {|}? I thought the \lvert \rvert were supposed to handle some kind of spacing.
Nov
16
comment Cause DeclarePairedDelimiter to switch starred and nonstarred versions
I appreciate your enthusiasm ("easy") :-) but it's not the 70s anymore and I find it horrific that I have to waste so much time learning (and using) a whole new programming language just because it's the traditional way to produce documents in my field, when software could easily take care of the details these days, and let me focus on the content.
Nov
15
comment Cause DeclarePairedDelimiter to switch starred and nonstarred versions
I suspected something like this (renewing the command and rewriting everything in an opposite manner) would work, but I'll leave the question open for a while since I'm hoping someone knows a more robust way to do it. (I.e. less likely to need a warranty, and less fragile - a stray key press while I have my pre header open won't make a change that's impossible for me to track down later when it breaks). :)
Nov
15
comment Cause DeclarePairedDelimiter to switch starred and nonstarred versions
@ChristianHupfer I'm thinking the starred version would then accept the optional argument as Arun says. I edited the question to clarify that it wouldn't be 'good' if this breaks some dependency in some popular package.
Nov
15
revised Cause DeclarePairedDelimiter to switch starred and nonstarred versions
added 57 characters in body
Nov
15
asked Cause DeclarePairedDelimiter to switch starred and nonstarred versions