patch 8.1.1547: functionality of bt_nofile() is confusing
Problem: Functionality of bt_nofile() is confusing.
Solution: Split into bt_nofile() and bt_nofilename().
diff --git a/src/buffer.c b/src/buffer.c
index e6ae09d..c3911ae 100644
--- a/src/buffer.c
+++ b/src/buffer.c
@@ -5698,7 +5698,7 @@
* buffer. This means the buffer name is not a file name.
*/
int
-bt_nofile(buf_T *buf)
+bt_nofilename(buf_T *buf)
{
return buf != NULL && ((buf->b_p_bt[0] == 'n' && buf->b_p_bt[2] == 'f')
|| buf->b_p_bt[0] == 'a'
@@ -5707,6 +5707,15 @@
}
/*
+ * Return TRUE if "buf" has 'buftype' set to "nofile".
+ */
+ int
+bt_nofile(buf_T *buf)
+{
+ return buf != NULL && buf->b_p_bt[0] == 'n' && buf->b_p_bt[2] == 'f';
+}
+
+/*
* Return TRUE if "buf" is a "nowrite", "nofile", "terminal" or "prompt"
* buffer.
*/
@@ -5772,7 +5781,7 @@
/* There is no _file_ when 'buftype' is "nofile", b_sfname
* contains the name as specified by the user. */
- if (bt_nofile(buf))
+ if (bt_nofilename(buf))
{
#ifdef FEAT_TERMINAL
if (buf->b_term != NULL)