The help page `?browser` says that typing `c` and hitting enter will get you out of the browser and let the function continue to run or typing `Q` and hitting enter will exit the browser and the function and take you back to the top-level prompt.

You will actually need to first enter f press enter and then enter Q. The order is finish and then quit. Otherwise you might not leave the browsing.

Turn off global debugging

    debuggingState(on=FALSE)

I am trying to build an R package so reading the manual on CRAN.
I could figure out that using imports to load functions in your namespace would be the best bet to use in the Description file.
After adding to the description file, I also added it to the namespace file.
I added importFrom to the namespace file with the functions required.

Now when I run R CMD check on my package,
I get an ERROR as
&gt;Namespace dependencies not required :
&gt;&#39;ggplot2&#39;

Further information : Even if I add the package to the Depends in the description file, they are not getting loaded.

Please help with this.

Please find my description file below

    Package: bigpackage
    Type: Package
    Title: Some title
    Version: 1.0
    Date: 2012-10-25
    Author: Mayank Bansal
    Maintainer: somename
    Imports : R(&gt;= 2.15.1), SweaveListingUtils( &gt;=0.5.5),xtable(&gt;=1.7-0),
            brew(&gt;=1.0-6), knitr(&gt;=0.8), RHive(&gt;= 0.0-6), ggplot2(&gt;=0.9.2)
            , brew, knitr
    SystemRequirements : LaTeX(texi2dvi) must be present in the system to
            create PDF reports
    Description: Some Description
    License: file LICENSE
    LazyLoad: yes
    ByteCompile: true
    OS_type : unix

Namespace dependencies not required

How can I show shadow for my linear layout. I want white colored rounded background with shadow around the linearlayout. I have done this so far. 

    &lt;LinearLayout
     android:layout_width=&quot;fill_parent&quot;
    android:layout_height=&quot;wrap_content&quot;
    android:layout_margin=&quot;10dp&quot;
    android:background=&quot;@xml/rounded_rect_shape&quot;
    android:orientation=&quot;vertical&quot;
    android:padding=&quot;10dp&quot;&gt;
    &lt;-- My buttons, textviews, Imageviews go here --&gt;
    &lt;/LinearLayout&gt;

And rounded_rect_shape.xml under xml directory

     &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;
    &lt;shape xmlns:android=&quot;http://schemas.android.com/apk/res/android&quot;
       android:shape=&quot;rectangle&quot; &gt;

       &lt;solid android:color=&quot;#ffffff&quot; /&gt;

       &lt;corners
          android:bottomLeftRadius=&quot;3dp&quot;
          android:bottomRightRadius=&quot;3dp&quot;
          android:topLeftRadius=&quot;3dp&quot;
          android:topRightRadius=&quot;3dp&quot; /&gt;
    &lt;/shape&gt;

How to show shadow around the linearlayout in Android?

I was trying to use the `browser()` command to debug earlier.

Right now, I kept getting the following in the console input window:

    Browse[13]&gt;

Is it possible to get out of this situation and just get back to  the normal console window?

How to leave the R browser() mode in the console window?

I was trying to use the <code>browser()</code> command to debug earlier.
Right now, I kept getting the following in the console input window:
<pre><code class="hljs language-css">Browse[13]>
</code></pre>
Is it possible to get out of this situation and just get back to the normal console window?

When I tried to connect R with Access database I get an error 

    odbcConnectAccess is only usable with 32-bit Windows

 

Does anyone has an idea how to solve this?


    library(RODBC) 
    mdbConnect&lt;-odbcConnectAccess(&quot;D:/SampleDB1/sampleDB1.mdb&quot;)



How to connect R with Access database in 64-bit Window?

I have been using Knitr via R-Studio, and think it is pretty neat. I have a minor issue though. When I source a file in an R-Chunk, the knitr output includes external comments as follows: 


    + FALSE Loading required package: ggplot2
    + FALSE Loading required package: gridExtra
    + FALSE Loading required package: grid
    + FALSE Loading required package: VGAM
    + FALSE Loading required package: splines
    + FALSE Loading required package: stats4
    + FALSE Attaching package: &#39;VGAM&#39;
    + FALSE The following object(s) are masked from &#39;package:stats4&#39;:

I have tried to set R-chunk options in various ways but still didn&#39;t seem to avoid the problem: 

    ```{r echo=FALSE, cache=FALSE, results=FALSE, warning=FALSE, comment=FALSE, warning=FALSE} 
    source(&quot;C:/Rscripts/source.R&quot;);
    
    ```

Is there any way to comment out these messages?



R - Markdown avoiding package loading messages

Is there an existing function to concatenate paths?

I know it is not that difficult to implement, but still... besides taking care of trailing `/` (or `\`) I would need to take care of proper OS path format detection (i.e. whether we write `C:\dir\file` or `/dir/file`). 

As I said, I believe I know how to implement it; the question is: should I do it? Does the functionality already exist in existing R package?

Function to concatenate paths?

Actual question
---------------

How do I avoid Rd file name conflicts when 

 1. a S4 generic and its method(s) are **not** necessarily all defined in the same package (package containing (some of) the custom method(s) depends on the package containing the generic) **and**
 2. using `roxygenize()` from package [roxygen2][1] to generate the actual Rd files?

I&#39;m not sure if this is a `roxygen2` problem or a common problem when the generic and its method(s) are scattered across packages (which IMHO in general definitely is a realistic use-case scenario if you follow a modular programming style). 

**What&#39;s the recommended way to handle these situations?**

Illustration
------------

**In package `pkga`**

Suppose in package `pkga` you defined a generic method `foo` and that you&#39;ve provided the respective roxygen code that `roxygenize()` picks up to generate the Rd file:

    #&#39; Test function
    #&#39; 
    #&#39; Test function.
    #&#39; 
    #&#39; @param ... Further arguments.
    #&#39; @author Janko Thyson \email{janko.thyson@@rappster.de}
    #&#39; @example inst/examples/foo.R
    #&#39; @docType methods
    #&#39; @rdname foo-methods
    #&#39; @export
    
    setGeneric(
        name=&quot;foo&quot;,
        signature=c(&quot;x&quot;),
        def=function(
             x,  
            ...
        ) {
        standardGeneric(&quot;xFoo&quot;)       
        }
    )

When `roxygenizing()` your package, a file called `foo-methods.Rd` is created in the `man` subdirectory that serves as the reference Rd file for all methods that might be created for this generic method. So far so good. If all of the methods for this generic are also part of your package, everything&#39;s good. For example, this roxygen code would make sure that documentation is added to `foo-methods.Rd` for the `ANY`-method of `foo`:

    #&#39; @param x \code{ANY}.
    #&#39; @return \code{TRUE}.
    #&#39; @rdname foo-methods
    #&#39; @aliases foo,ANY-method
    #&#39; @export
    
    setMethod(
        f=&quot;foo&quot;, 
        signature=signature(x=&quot;ANY&quot;), 
        definition=cmpfun(function(
            x,
            ...
        ) {
        return(TRUE)
        }, options=list(suppressAll=TRUE))
    )

However, if package `pkga` provides the generic for `foo` and you decide in some other package (say `pkgb`) to add a `foo`-method for `x` being of class `character`, then `R CMD check` will tell you that there is a name clash with respect to Rd file names and/or aliases (as there already exists a Rd file `foo-methods.Rd` in `pkga`):

**In package `pkgb`**

    #&#39; @param x \code{character}.
    #&#39; @return \code{character}.
    #&#39; @rdname foo-methods
    #&#39; @aliases foo,character-method
    #&#39; @export
    
    setMethod(
        f=&quot;foo&quot;, 
        signature=signature(x=&quot;character&quot;), 
        definition=cmpfun(function(
            x,
            ...
        ) {
        return(x)
        }, options=list(suppressAll=TRUE))
    )

To be more precise, this is the error that&#39;s thrown/written to file `00install.out`

    Error : Q:/pkgb/man/foo-methods.Rd: Sections \title, and \name must exist and be unique in Rd files
    ERROR: installing Rd objects failed for package &#39;pkgb&#39;


Due dilligence
--------------

I tried to change the values for `@rdname` and `@aliases` to `foo_pkgb*` (instead of `foo*`), but `\title` and `\name` still are set to `foo` when roxygenizing and thus the error remains. Any ideas **besides manually editing the Rd files** generated by `roxygenize()`?


----------


EDIT 2012-12-01
---------------

In light of starting the bounty, the actual question might get a slightly broader flavor: 

**How can we implement some sort of an &quot;inter-package&quot; check with respect to Rd files and/or how can we consolidate S4 method help files scattered across packages into one single Rd file in order to present a single source of reference to the end-user?**


  [1]: http://cran.r-project.org/web/packages/roxygen2/index.html

Rd file name conflict when extending a S4 method of some other package

When stepping through JavaScript code in Google Chrome debugger, how do I terminate script execution if I do not want to continue? The only way I found is closing the browser window.

Pressing &quot;Reload this page&quot; runs the rest of the code and even submits forms as if pressing F8 &quot;Continue&quot;.

**UPDATE**: 

When pressing F5 (Refresh) while a script is paused:

- Google Chrome (v22) runs the script. If the script submits HTTP request, the HTTP response for that request is displayed. The original page is not refreshed.
- IE 9 just freezes. However IE has an option &quot;Stop Debugging&quot; which, when pressed (provided you did not press F5 earlier), continues to run the script outside debugger.
- Firebug behaves identically to Chrome.

Closing and then opening again the browser window is not always the next easiest way
because it will kill browser session state and that may be important. All your breakpoints are also lost.

**UPDATE (Jan 2014)**: 

Refresh while debugging:

- Chrome v31: lets scripts to run and stops on further breakpoints (but does not submit ajax requests), then refreshes.
- IE 11: refresh does nothing, but you can press F5 to continue.
- Firefox v26: lets scripts to run but does not stop on further breakpoints, submits ajax requests, then refreshes.

Kind of progress!

Navigate to the same page while debugging:

- Chrome v31: same as Refresh.
- IE 11: scripts are terminated, new browser session is started (same as closing and opening again).
- Firefox v26: nothing happens.

Also *juacala* suggested an effective workaround. For example, if you are using jQuery, running **delete $** from console will stop execution once any jQuery method is encountered. I have tested it in all above browsers and can confirm it is working.

**UPDATE (Mar 2015)**: 

Finally, after over 2 years and almost 10K views, the right answer was given by Alexander K. Google Chrome has its own Task Manager which can kill a tab process *without* closing the tab itself, keeping all the breakpoints and other stuff intact.

I even went as far as BrowserStack.com to test it in Chrome v22 and found that this was working this way even at that time.

Juacala&#39;s workaround is still useful when debugging in IE or Firefox.

**UPDATE (Jan 2019)**:


Chrome Dev Tools at last added a proper way to stop script execution which is nice (although a bit hidden). Refer to James Gentes&#39;s answer for details.

How to terminate script execution when debugging in Google Chrome?

In C we write code like

    #ifdef DEBUG
    printf(&quot;Some debug log... This could probably be achieved by python logging.Logger&quot;);
    /* Do some sanity check code */
    assert someCondition
    /* More complex sanitycheck */
    while(list-&gt;next){
    assert fooCheck(list)
    }
    
    #endif

Is there a way to do this in python?

Edit: I got my answer, and more :)
Paolo, Steven Rumbalski and J Sebastian gave me the information I was looking for. Thanks das for the detailed answer, although I&#39;ll probably not use a preprocessor right now.

J Sebastian, whose comment got deleted because the answer in which he posted his comment, deleted his answer I think.
He said I could use the isEnabledFor() method in Logger to feed a conditional.

Thanks everyone for your inputs. This is my first question. I wish I could accept paolo, or j sebastian&#39;s answers. But since those were offered as comments, I&#39;ll accept das&#39; answer.


I will probably use either http://nestedinfiniteloops.wordpress.com/2012/01/15/if-debug-python-flavoured/ or Logger.isEnabledFor()

Python equivalent for #ifdef DEBUG

Consider the following Linux kernel dump stack trace; e.g., you can trigger a panic from the kernel source code by calling `panic(&quot;debugging a Linux kernel panic&quot;);`:

```none
[&lt;001360ac&gt;] (unwind_backtrace+0x0/0xf8) from [&lt;00147b7c&gt;] (warn_slowpath_common+0x50/0x60)
[&lt;00147b7c&gt;] (warn_slowpath_common+0x50/0x60) from [&lt;00147c40&gt;] (warn_slowpath_null+0x1c/0x24)
[&lt;00147c40&gt;] (warn_slowpath_null+0x1c/0x24) from [&lt;0014de44&gt;] (local_bh_enable_ip+0xa0/0xac)
[&lt;0014de44&gt;] (local_bh_enable_ip+0xa0/0xac) from [&lt;0019594c&gt;] (bdi_register+0xec/0x150)
```

 - In `unwind_backtrace+0x0/0xf8` what does `+0x0/0xf8` stand for?
 - How can I see the C code of `unwind_backtrace+0x0/0xf8`?
 - How to interpret the panic&#39;s content?  

How to read, understand, analyze, and debug a Linux kernel panic?

Currently, I package the release builds with Nuget for the official builds to nuget.org, but I package the debug builds with Nuget for the symbol source pushes to symbolsource.org.

EDIT: (Jon Skeet, with some bias from Noda Time development)

NuGet now supports pushing to both NuGet gallery *and* symbolsource.org (or similar servers), [as documented][1]. Unfortunately, there are two contradictory requirements here:

- When just *using* a library without any need for debugging, you really want a release build. That&#39;s what release builds are for, after all.
- When debugging into a library for diagnostic purposes, you really want a debug build with all the appropriate optimizations disabled. That&#39;s what debug builds are for, after all.

That would be fine, but NuGet doesn&#39;t (as far as I can tell) allow both the release and debug builds to be published in a useful way, in the same package.

So, the choices are:

- Distribute the debug builds to everyone (as shown in the example in the docs) and live with any size and performance hits. 
- Distribute the release builds to everyone and live with a slightly impaired debug experience.
- Go for a really complicated distribution policy, potentially providing separate release and debug packages.

The first two really boil down to the effect of the differences between debug and release builds... although it&#39;s worth noting that there&#39;s also a big difference between wanting to step into the code of a library because you want to check some behaviour, and wanting to debug the code of a library because you believe you&#39;ve found a bug. In the second case, it&#39;s probably better to get the code of the library *as a Visual Studio solution* and debug that way, so I&#39;m not paying too much heed to that situation.

My temptation is to just keep with the release builds, with the expectation that *relatively* few people will need to debug, and the ones who do won&#39;t be impacted *much* by the optimizations in the release build. (The JIT compiler does most of the optimizing anyway.)

So, are there other options we hadn&#39;t considered? Are there other considerations which tip the balance? Is pushing NuGet packages to SymbolSource sufficiently new that &quot;best practice&quot; really hasn&#39;t been established?

  [1]: http://docs.nuget.org/docs/creating-packages/creating-and-publishing-a-symbol-package

Best practices with Nuget: Debug or Release?

I am trying to use the node debugger.
I am running `node debug server` to run my server. Then I have:

    ...
    var Workspace = mongoose.model(&#39;Workspace&#39;);
    debugger;

At this point, as expected, when I run this code the debugger pops up.
However, I would expect it to have all of the current variables set, like it happens in Chrome&#39;s own debugger.

But:

    break in hotplate/node_modules/bd/lib/bd.js:133
    132 
    133   debugger;
    134 
    135   // Delete the ID and the version since there&#39;s no point,
    debug&gt; Workspace
    ReferenceError: Workspace is not defined

So... how do I _actually_ inspect the current variables?

Bonus question: is there ANY way to use Chrome&#39;s developers tools (CTRL-J) so that it connects to the node and works that way? (I am aware of node-inspector, but it&#39;s very outdated and...)

Content Type	Original Author	Original Content on Stackoverflow
Question	user1769197	View Question on Stackoverflow
Solution 1 - R	Greg Snow	View Answer on Stackoverflow
Solution 2 - R	MAec	View Answer on Stackoverflow
Solution 3 - R	mlworker	View Answer on Stackoverflow

How to leave the R browser() mode in the console window?

R Problem Overview

R Solutions

Solution 1 - R

Solution 2 - R

Solution 3 - R

How to show shadow around the linearlayout in Android?

Namespace dependencies not required

Attributions