feature request: deluxetable to accept p{} and other column specifiers, docs to list shortcomings

[joeharr4]

Please enable p{} column specifiers in deluxetables. And any other standard table or AAS table specifiers.

Until they are there, the docs should outline the limitations of deluxetable, including the lack of column-width control, the inability to use \edit#{} macros, and any other limitations below what the standard LaTeX table environment handles. A feature-comparison table would be nice. Building a large table takes a lot of time, and discovering later that you have to reformat it into a different kind of table is very frustrating (and error-prone)! Please let your users make an informed choice. Given that revisions are frequent, perhaps deluxetables should no longer be so strongly encouraged in the docs, until that bug is fixed.

Thanks,

--jh--

[augustfly]

Please provide a MWE for a non-functional instance of p{} in a deluxetable. I find many working examples of p{} in deluxetables submitted by authors. As stated in the documentation, section 2.16.2 https://journals.aas.org/aastexguide/#preamble_deluxetable:

If more complicated column headings are required, any valid tabular command that constitutes a proper head line in a LATEX table may be used.

Please segregate the request for warnings/feature comparisons about deluxetable to a separate issue, or I will. It is most helpful to have 1 topic per issue. If the documentation issue is centered on the \edit problem then please move the request for a bug warning in the documentation there.