-
Notifications
You must be signed in to change notification settings - Fork 61
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
Support resizebox for etable #520
Comments
etable already has so many arguments. |
@waynelapierre It's not something you want to do if you have many tables and want to set it programmatically. |
@matthewgson Sure, if you need more granular control of the table layout, wouldn't it make more sense to tune LaTeX codes than to make etable even more bloated? |
Sure, but you could make your own helper function that takes the output of wrap_in_resizebox <- function(x) {
paste0("\\\resizebox{\\\linewidth}{!}{\n", x, "\n}")
}
etable(..., tex = TRUE) |>
wrap_in_resizebox() |>
writeLines(file = "output.tex") (I didn't try this code, but this idea should work) |
@waynelapierre Not really. I think it is a simple change from the current flow that won't make it bloated if it ever were. etable is designed to be the finalizer of the workflow, not the pipeline I don't think it would be a design problem either. It's completely up to the maintainer's view. @etiennebacher The resizebox should be inside the table boundary and it's pretty messier than it seems. Of course, there should be a way to augment them similar to your suggestion, but adding them similar to adjustbox would be greater. |
I would like to express my gratitude for the exceptional work you have done on this project.
Although I'm aware
adjustbox
is more flexible and has powerful features compared to similarresizebox
, I've been somewhat more successful with resizebox when it comes to adjusting the tables in my paper. I was wondering if there's any chance this option could be added for regression tables (etable)?The text was updated successfully, but these errors were encountered: