string - How do you format multiline R package messages? -


in developing r package, use r's message() or warning() functions produce output package user.

sometimes these messages can long. can (text trivial example):

message("if got point in code, means matrix empty. calculation continues should consider re-evaluating earlier step in process")

great... style, want lines of code less 80 characters, fit nicely in narrow screens, on github, etc. , can use ide code reflow tool reformat message if changes.

so try this:

message("if got point in code, means  matrix empty. calculation continues should consider  re-evaluating earlier step in process")

this solves code criteria -- less 80 character lines , can reflow expected. sticks whitespace right in message output, don't want:

if got point in code, means  matrix empty. calculation continues should consider  re-evaluating earlier step in process

so found handy function called strwrap() seems solve problem:

message(strwrap("if got point in code, means  matrix empty. calculation continues should consider  re-evaluating earlier step in process"))

output:

if got point in code, means matrix empty.  calculation continues should considerre-evaluating earlier  step in process

looks nice -- eliminated space between "consider" , "re-evaluating" because space @ newline.

another alternative break chunks in code:

message("if got point in code, means ",  "the matrix empty. calculation continues should consider ", "re-evaluating earlier step in process")

this makes output correct, text can no longer reflow ide, etc, because it's not 1 string, doesn't work me on dev side.

so: how can make nicely formatted message lets me write message across lines?

i have written function:

.nicemsg = function(...) {     message(paste(strwrap(...), collapse="\n")) }

is there better way using built-in don't have include function in every r package write?

using couple more arguments strwrap makes possible

message(strwrap(..., prefix = " ", initial = ""))

you might able improve readability playing order of arguments. i'm not sure if better or not.

message(strwrap(prefix = " ", initial = "",    "if got point in code, means  matrix empty. calculation continues should consider  re-evaluating earlier step in process"))

or, if prefer wrapping it

tidymess <- function(..., prefix = " ", initial = ""){   message(strwrap(..., prefix = prefix, initial = initial)) }

Comments

Post a Comment

Popular posts from this blog

android - InAppBilling registering BroadcastReceiver in AndroidManifest -

i'm implementing inapp billing in android app. works well, however, i'm trying decouple broadcast receiver activity manifest. suggestion in android's trivialdrive sample: // important: dynamically register broadcast messages updated purchases. // register receiver here instead of <receiver> in manifest // because call getpurchases() @ startup, therefore can ignore // broadcasts sent while app isn't running. // note: registering listener in activity bad idea, done here // because sample. regardless, receiver must registered after // iabhelper setup, before first call getpurchases(). currently there's class extends broadcastreceiver : public class iabbroadcastreceiver extends broadcastreceiver { /** * intent action receiver should filter for. */ public static final string action = "com.android.vending.billing.purchases_updated"; private final iabbroadcastlistener mlistener; public iabbroadcastreceiver(iabbroadcastlistener listener) { m...
Read more

python Tkinter Capturing keyboard events save as one single string -

is possible store keyboard events 1 string? code below stores 1 char , prints it. card reader or bar code reader, contains collection of character/ string not 1 character @ time. goal save char pressed text variable. from tkinter import * root = tk() def key(event): text= event.char text+= event.char print ("pressed", text) def callback(event): frame.focus_set() print ("clicked at", event.x, event.y) frame = frame(root, width=100, height=100) frame.bind("<key>", key) frame.bind("<button-1>", callback) frame.pack() root.mainloop() currently, creating text variable , everytime key() function gets called, , text stores last character typed. you can define text module level variable , , use module level text inside key function - text = '' def key(event): global text text+= event.char print("pressed", text)
Read more

sql server - Why does Linq-to-SQL add unnecessary COUNT()? -

here tables: create table customer ( cid int primary key, name varchar(32) ) create table ord ( oid int primary key, cid int foreign key references customer, address varchar(20) ) here's linq-to-sql statement: var aaa = c in db.customer select new { c, o = c.ord.tolist() }; and here's inexplicable query generated linq-to-sql: select [t0].[cid] [cid], [t0].[name] [name], [t1].[oid] [oid], [t1].[cid] [cid2], [t1].[address] [address], (select count(*) [dbo].[ord] [t2] [t2].[cid] = [t0].[cid]) [value] [dbo].[customer] [t0] left outer join [dbo].[ord] [t1] on [t1].[cid] = [t0].[cid] order [t0].[cid], [t1].[oid] i want understand how rid of count(*) part. it's entirely uncalled for! linq needs count(*) in order determine number of entries returned o = c.ord.tolist() .
Read more