🔍 An RStudio addin slash regex utility belt
Vous ne pouvez pas sélectionner plus de 25 sujets Les noms de sujets doivent commencer par une lettre ou un nombre, peuvent contenir des tirets ('-') et peuvent comporter jusqu'à 35 caractères.

72 lines
2.8KB

  1. % Generated by roxygen2: do not edit by hand
  2. % Please edit documentation in R/addins.R, R/gadget.R
  3. \name{regexplain_file}
  4. \alias{regexplain_file}
  5. \alias{regexplain_gadget}
  6. \alias{regexplain_web}
  7. \title{RegExplain gadget}
  8. \usage{
  9. regexplain_file(pattern = NULL, start_page = "RegEx")
  10. regexplain_gadget(text = NULL, pattern = NULL, start_page = if
  11. (is.null(text)) "Text" else "RegEx")
  12. regexplain_web(text = NULL, pattern = NULL, start_page = "Text", ...)
  13. }
  14. \arguments{
  15. \item{pattern}{Regular Expression to edit or visualize using RegExplain}
  16. \item{start_page}{Open gadget to this tab, one of \code{"Text"}, \code{"RegEx"},
  17. \code{"Output"}, or \code{"Help"}}
  18. \item{text}{Text to explore in gadget (editable using interface)}
  19. \item{...}{Arguments passed on to \code{shiny::shinyApp}
  20. \describe{
  21. \item{ui}{The UI definition of the app (for example, a call to
  22. \code{fluidPage()} with nested controls)}
  23. \item{server}{A server function}
  24. \item{onStart}{A function that will be called before the app is actually run.
  25. This is only needed for \code{shinyAppObj}, since in the \code{shinyAppDir}
  26. case, a \code{global.R} file can be used for this purpose.}
  27. \item{options}{Named options that should be passed to the \code{runApp} call
  28. (these can be any of the following: "port", "launch.browser", "host", "quiet",
  29. "display.mode" and "test.mode"). You can also specify \code{width} and
  30. \code{height} parameters which provide a hint to the embedding environment
  31. about the ideal height/width for the app.}
  32. \item{uiPattern}{A regular expression that will be applied to each \code{GET}
  33. request to determine whether the \code{ui} should be used to handle the
  34. request. Note that the entire request path must match the regular
  35. expression in order for the match to be considered successful.}
  36. \item{enableBookmarking}{Can be one of \code{"url"}, \code{"server"}, or
  37. \code{"disable"}. This is equivalent to calling the
  38. \code{\link{enableBookmarking}()} function just before calling
  39. \code{shinyApp()}. With the default value (\code{NULL}), the app will
  40. respect the setting from any previous calls to \code{enableBookmarking()}.
  41. See \code{\link{enableBookmarking}} for more information.}
  42. }}
  43. }
  44. \description{
  45. The function behind the RegExplain Selection and RegExplain File
  46. addins. Opens the RegExplain gadget interface in an RStudio viewer
  47. pane.
  48. }
  49. \section{Functions}{
  50. \itemize{
  51. \item \code{regexplain_file}: Opens file chooser to pick file, reads lines,
  52. returns first \code{regexplain.addin.max_lines} (default 100). Used in the
  53. "Regexplain File" \link{regexplain_addin}.
  54. \item \code{regexplain_web}: Launches the RegExplain gadget in a browser or an
  55. RStduio viewer pane.
  56. }}
  57. \examples{
  58. \dontrun{
  59. regexplain_gadget(text = month.name, pattern = "(Ma|Ju)|(er)")
  60. regexplain_web(text = month.name, pattern = "(Ma|Ju)|(er)")
  61. regexplain_file()
  62. }
  63. }