-
-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Duplicated rows cause unexpected output with group_rows #161
Comments
Hi, @steveputman thanks for raising this before I release this version to CRAN. |
Got it—thanks for trying. I have been trying to think about other workarounds (in my case, I can typically structure the duplicated rows out of my table, though that obviously won’t work for many cases.) I did wonder if an additional column could be added with identifiers (like row numbers) that could then be suppressed in TeX.
From: Hao Zhu <notifications@github.com>
Reply-To: haozhu233/kableExtra <reply@reply.github.com>
Date: Thursday, April 5, 2018 at 12:15 PM
To: haozhu233/kableExtra <kableExtra@noreply.github.com>
Cc: Steve Putman <steve.putman@gmail.com>, Mention <mention@noreply.github.com>
Subject: Re: [haozhu233/kableExtra] Duplicated rows cause unexpected output with group_rows (#161)
Hi, @steveputman<https://github.com/steveputman> thanks for raising this before I release this version to CRAN. I look into the problem and found that I can't put vphantom at the end of the line as it will take away the ability to identify duplicated rows. I will change it back to putting it after the first &.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#161 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AEvGHDgZ8ZJ6qn4XgXVpd34snQz6q--eks5tllEtgaJpZM4TH6ez>.
|
Hmm, so in the end I changed it back to the location after first |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I was testing your earlier commit to see if it fixed my old problem referenced in #145 . Something strange is happening.
Knitting
outputtable
gets you this:(In my actual case, I get these behaviors--dropped/out-of-order labels and improperly indented first columns--as well as "narrowed"
\toprule
,\midrule
, and\bottumrule
that do not extend to the width of the table data.) I am not a tex debugger unfortunately, but I did notice that the addedvphantom
are being aggregated at the end of one line rather than spread across the duplicated rows. Also some strange behavior that may tie in torepeat_headers
? You get the "continued" tex even when you haven't broken across a page, though it doesn't seem to show up in the caption?Thanks again for your help and sorry to pester you on this, but kableExtra has become indispensable ever since I discovered it!
Steve
The text was updated successfully, but these errors were encountered: