[elpa] externals/beframe 0bbd2e62e6 17/19: Set beframe-functions-in-frames to nil by default

[ELPA Syncer]

branch: externals/beframe
commit 0bbd2e62e614a380db7aaff119ba5820d5a96bbf
Author: Protesilaos Stavrou <info@protesilaos.com>
Commit: Protesilaos Stavrou <info@protesilaos.com>

    Set beframe-functions-in-frames to nil by default
---
 README.org | 9 +++++----
 beframe.el | 2 +-
 2 files changed, 6 insertions(+), 5 deletions(-)

diff --git a/README.org b/README.org
index be45f5bb92..40f8630d16 100644
--- a/README.org
+++ b/README.org
@@ -102,10 +102,11 @@ The ~beframe-mode~ does the following:
  #+vindex: beframe-functions-in-frames
 - When the user option ~beframe-functions-in-frames~ contains a list
   of functions, it makes them run with ~other-frame-prefix~, meaning
-  that they are called in a new frame.  The default value of that
-  user option affects the =project.el= project-switching selection:
-  the new project buffer appears in its own frame and, thus, becomes
-  part of a beframed list of buffers, isolated from all other frames.
+  that they are called in a new frame.  For example, the user can add
+  a list that includes ~project-prompt-project-dir~ from the built-in
+  ~project~ library.  With that the new project buffer appears in its
+  own frame and, thus, becomes part of a beframed list of buffers,
+  isolated from all other frames.
 
 Development note: ~beframe~ is in its early days.  The minor mode may
 be revised to have more features and/or greater flexibility.
diff --git a/beframe.el b/beframe.el
index dd180a691c..a87e5ca3b8 100644
--- a/beframe.el
+++ b/beframe.el
@@ -107,7 +107,7 @@ Otherwise framed buffers are limited to the frame that uses 
them."
   :package-version '(beframe . "0.1.0")
   :type '(repeat string))
 
-(defcustom beframe-functions-in-frames (list (compat-function 
project-prompt-project-dir))
+(defcustom beframe-functions-in-frames nil
   "Functions that use new frame when `beframe-mode' is enabled.
 
 When `beframe-mode' is enabled, install advice around each